Website profiles · Technology insights · Alternatives

midi-recorder.web.app

No paid content found
Visit website
Profile views 8 Outbound visits 1 Normal
MIDI Recorder Full homepage screenshot

At a glance

Category
Resources & Utilities
Language
English
Paid-content signal
No paid content foundObserved
Registered
2019
Hosting
FastlyInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is MIDI Recorder?

MIDI Recorder is a browser-based tool for capturing what you play on a MIDI keyboard and saving it as a MIDI file. You plug in a MIDI device, play, and the app records the notes; you can then export a .mid file, undo or clear takes, and recover earlier recordings.

What it does

  • Records live MIDI input from a connected keyboard or controller.
  • Exports the performance as a standard MIDI file, which you can open in a DAW or notation app.
  • Offers basic take management: Clear, Undo, and Recover Recordings for retrieving previous sessions.

Who it suits

  • Keyboardists who want a quick sketchpad without opening a full DAW.
  • Students or teachers capturing short exercises to share as .mid files.
  • Anyone on a computer with a MIDI keyboard who needs a zero-install recording step.

Practical trade-offs

  • It records MIDI events, not audio, so playback depends on whatever instrument or software you load the file into.
  • It runs in the browser and needs MIDI access; the page itself notes that support varies, recommending Chrome or, on other browsers, the Jazz-Soft Web MIDI API extension.
  • It is a capture-and-export tool rather than an editor: expect to do arranging, quantizing and mixing elsewhere.

Next step Connect your keyboard, confirm it appears under MIDI devices, play a short phrase, then use Export → Save MIDI File and open the result in your DAW to check timing and note data. If the device doesn't appear, the page suggests checking the connection and power, refreshing, replugging, or restarting the computer.

How do I record MIDI from my keyboard using this app?

Connect a MIDI keyboard, open the app, press Record, play, then press Stop and export a MIDI file. The app describes itself as "the easiest way to record MIDI" and its main prompt is "Plug in a MIDI keyboard and play away!" — so it is built for exactly this task.

Steps

  1. Connect your keyboard by USB (or via an audio/MIDI interface) and turn it on before opening the page. The app checks for devices on load and shows them under "MIDI devices".
  2. Open the app in a browser that supports the Web MIDI API. The page warns that unsupported browsers should use Chrome, or the Jazz-Soft Web MIDI API extension elsewhere.
  3. Confirm your device appears in the MIDI device list. If it shows "No MIDI devices detected", check the connection and refresh.
  4. Press Record, then play. Notes are captured as you perform; the interface includes Stop, Clear, Undo and Recover Recordings controls.
  5. Stop recording, review what you played, and use Undo or Clear to fix mistakes. "Recover Recordings" suggests you can retrieve earlier takes if you lose one.
  6. Export with "Save MIDI File" to download your performance as a standard MIDI file. That file can then be opened in a DAW or notation program for editing, quantising or instrument changes.

If your keyboard doesn't show up

The app's own troubleshooting list is short and worth following in order:

  • Make sure the keyboard is plugged in and switched on.
  • Refresh the page.
  • Unplug and replug the device.
  • Restart your computer.

If none of that works, the problem is usually the browser rather than the keyboard — Web MIDI support varies, and the app explicitly points to Chrome or the Jazz-Soft extension as fallbacks.

What this app is and isn't

You get You don't get
Quick capture of note data from a MIDI keyboard Audio recording of your keyboard's sound
A downloadable .MID file Built-in editing, mixing or virtual instruments
A browser-based tool with no install step Guaranteed support in every browser

The key distinction: this records MIDI data (which notes, when, how hard), not sound. If you want to hear your performance later, you'll need to open the exported file in software that can play it back through an instrument.

Practical scenario

Say you're sketching a piano idea at your desk and don't want to boot a full DAW. Plug in the keyboard, open MIDI Recorder, capture the take, export the MIDI file, and drop it into your main production software later. It suits fast idea capture, practising with a written record of what you played, or grabbing a part on a machine where you can't install software.

If you need multitrack arrangement, sound design or audio fidelity, this is the wrong tool — go straight to a DAW. Use this when the goal is a clean, portable MIDI file in as few steps as possible.

Which browsers and MIDI devices are compatible with MIDI Recorder?

MIDI Recorder is a browser-based tool for capturing MIDI input from a connected keyboard and exporting it as a MIDI file. Compatibility depends on two separate things: the browser's support for the Web MIDI API, and whether your MIDI device is recognized by your operating system.

Browser compatibility

The app's own on-screen guidance points to Chrome as the recommended browser. If you are using a different browser, it suggests the Jazz-Soft Web MIDI API extension as a workaround. The page also displays a message when the browser lacks MIDI access entirely, so the app is transparent about this limitation rather than silently failing.

In practice, this means:

  • Chrome — the intended path; MIDI access should work without add-ons.
  • Other browsers — may work only if you install the suggested extension. Results vary by browser and platform.
  • Browsers without Web MIDI support — the app cannot detect devices at all, and you will see the "This browser doesn't support MIDI access" notice.

MIDI device compatibility

The page does not list specific supported models. Instead, it shows a "MIDI devices" area that loads detected devices and reports "No MIDI devices detected" when nothing is found. Any MIDI keyboard or controller that your computer recognizes as a MIDI input device should appear there — the app works with what the browser can see, not with a fixed hardware list.

If your device does not appear

The app offers a short troubleshooting sequence on the page itself:

  1. Confirm the device is plugged in and powered on.
  2. Refresh the page.
  3. Unplug and replug the device.
  4. Restart your computer.

If you are on a browser other than Chrome, try Chrome first before working through the hardware steps — that isolates a browser problem from a device problem.

Practical next step

Before relying on this for a session, open the page in Chrome with your keyboard connected and check that the device name appears in the MIDI devices list. If it does, record a few notes and use Export to save a MIDI file to confirm the full round trip works. If the device never appears, the issue is almost certainly browser support or the operating system's MIDI driver rather than the app. For background on the underlying standard, see MDN Web Docs and Chrome Recorder if you also need audio capture alongside MIDI.

How can I export and save my recorded MIDI as a file?

Use the Save MIDI File control in the Export area of MIDI Recorder to write your recorded notes to a standard MIDI file. The page's own wording pairs "Export" with "Save MIDI File," so the intended flow is: record, then save from that section rather than looking for a separate download page.

Practical workflow

  1. Confirm your keyboard is detected under Input — the page shows "MIDI devices: Loading..." and warns "No MIDI devices detected" when nothing is found.
  2. Record your performance; the interface tracks note activity and shows "No notes recorded" when the take is empty.
  3. Open the Export section and choose Save MIDI File.
  4. Your browser will handle the file save; the resulting .mid file is what you can drag into a DAW, notation app or media player.

If the save button seems to do nothing, check that notes were actually captured first. A file with no notes is not useful, and the "No notes recorded" state is the clearest signal to re-record.

Two related controls worth knowing

  • Undo and Clear affect the current take, so use them before exporting if you want to trim mistakes rather than after.
  • Recover Recordings suggests the app keeps some session history; if a take disappears, try recovering before re-recording. Treat this as a convenience, not a guarantee — save anything important as soon as you are happy with it.

Browser note

The page itself says MIDI access depends on browser support, recommending Chrome or the Jazz-Soft Web MIDI API extension elsewhere. Since export happens in the same page context, if recording works, saving should too; if MIDI access fails entirely, there will be nothing to export.

Next step: after saving, open the .mid file in your DAW to verify the note timing and channel data, since a quick check there catches anything the browser capture missed.

How do I recover a recording if I accidentally clear it?

Use the Recover Recordings button in the app. MIDI Recorder keeps cleared takes and lets you bring them back from that control.

How recovery works here

  • Clear removes the current notes from the view.
  • Recover Recordings brings back a cleared take.
  • If nothing is available, it shows No more recordings to recover.
  • Undo may also help if you catch the mistake immediately.

Practical steps

  1. Stop recording first.
  2. Click Recover Recordings.
  3. If the take returns, export it right away with Save MIDI File.
  4. If the button says there is nothing to recover, refresh the page and try again while the session is still open.

Decision criterion

Treat recovery as a short-term safety net, not a file archive. If the take matters, save the MIDI file as soon as you finish it. For browser-based MIDI tools generally, check that your browser supports MIDI access and that the keyboard is connected before recording, since a failed connection can make it look like a take was lost.

A concrete scenario: you record a piano part, click Clear by mistake, then click Recover Recordings. If it returns, immediately use Save MIDI File so the take lives on your computer rather than only in the browser session.

What should I do if my MIDI keyboard isn't detected by the app?

Work through the checks in order, from fastest to slowest. The app itself lists the likely culprits: the device being off or unplugged, the page needing a refresh, or the browser lacking MIDI access.

Quick checklist

  1. Confirm the keyboard is powered on and physically connected to the computer. Many keyboards have a separate power switch or need USB bus power that a weak hub won't supply.
  2. Refresh the page. Web MIDI permission and device enumeration are established when the page loads, so a keyboard connected afterward often won't appear until you reload.
  3. Unplug the keyboard and plug it back in, then refresh again.
  4. Restart the computer if the device still doesn't appear anywhere.

If the app says your browser doesn't support MIDI access

This is a browser problem, not a keyboard problem. The app recommends Chrome, or for other browsers the Jazz-Soft Web MIDI API extension. In practice, Chrome and other Chromium-based browsers have the most reliable Web MIDI support; Firefox and Safari users are the ones most likely to hit this message. Also check that you granted the MIDI permission prompt when it appeared — a blocked permission looks identical to an unsupported browser from the app's point of view.

If the keyboard shows up elsewhere but not here

Test it in another MIDI-capable tool, such as a DAW or a browser-based piano. If it appears there, the issue is the browser or the page session; if it doesn't, the issue is the cable, port, driver or the keyboard itself. Swapping the USB cable and trying a different port (directly on the computer rather than through a hub) resolves a surprising share of these cases.

Before you troubleshoot further

If you were mid-session, the app's Clear and Undo controls affect what's currently recorded, and there's a Recover Recordings option for bringing back previous takes — worth knowing before you start clearing or reloading in frustration. Once notes are captured, use Export / Save MIDI File to write them out, so a later browser hiccup doesn't cost you the performance.

A sensible decision rule: if the app reports no MIDI devices at all, treat it as a hardware or connection issue first; if it reports that the browser doesn't support MIDI access, treat it as a browser issue and switch to Google Chrome before touching cables.

Related questions

More questions →
Can I recover recordings in MIDI Recorder?

Yes — MIDI Recorder has a Recover Recordings option, so clearing or undoing your take doesn't necessarily mean it's gone for good. The important condition is that recovery is a browser-session feature: it restores recordings the app still holds, and you should export the one you want as a MIDI file right after recovering it. If you close the tab, reload the page, or clear browser data, that safety net is not something you can count on.

What "Recover Recordings" does

MIDI Recorder is a browser-based tool that records what you play on a connected MIDI keyboard. Alongside the recording controls, the interface includes a Recover Recordings action. When you open it, it either shows recordings you can bring back or tells you "No more recordings to recover."

That message is the key signal: recovery works from a limited store of previous takes, not from an unlimited history. Once that store is exhausted, there is nothing left to restore.

When a recording becomes recoverable

A take ends up in the recoverable pool when it is removed from the current session without being exported. In practice that means:

  • You pressed Clear and wiped the notes you had just recorded.
  • You used Undo to step back past a recording.
  • You recorded a new take over a previous one instead of saving it first.

If you exported the take with Save MIDI File before clearing it, you already have the file on your computer and don't need recovery at all.

Clear vs. Undo: what each one affects

Action What it does Effect on recovery
Clear Removes the notes currently held in the session The cleared take can become available under Recover Recordings
Undo Steps back through your recent edits or recording actions Undone material can also land in the recoverable pool
Recover Recordings Brings back a previously removed take Restores it into the session so you can work with it again
Save MIDI File Exports the current notes as a .mid file Permanent — this is the only copy that survives closing the browser

The distinction that matters: Clear and Undo change what's in front of you, while Recover Recordings reaches back for it. Save MIDI File is the only step that moves your performance out of the browser entirely.

How to recover a recording

  1. Connect your MIDI keyboard and confirm it appears in the MIDI devices list.
  2. Open Recover Recordings.
  3. If a take is listed, select it to restore it into the session.
  4. Play it back or check the note display to confirm it's the take you wanted.
  5. Immediately use Save MIDI File to export it.

Step 5 is not optional if the recording matters to you. Recovery puts the notes back in the app; only the export puts them on your disk.

Common snags

"No more recordings to recover." The recoverable store is empty — either you already restored everything, or the take was never in a state the app could hold onto. Nothing further can be done in that session.

You reloaded the page first. Recovery depends on the app's current state. Refreshing or closing the tab before recovering is the most common way to lose a take for good.

The MIDI device isn't detected. Recovery and recording both need MIDI access. If the device list shows "No MIDI devices detected," check that the keyboard is plugged in and powered on, then refresh the page. If you see "This browser doesn't support MIDI access," switch to Chrome or install the Jazz-Soft Web MIDI API extension for your browser.

You cleared, then recorded something new. The newer take occupies the session. Recover the older one first, export it, then return to what you were working on.

The habit that makes recovery unnecessary

Treat Save MIDI File as the end of every good take, not as something to do at the end of a session. Recovery is a convenience for the take you just cleared by accident — it is not a project file, and it does not follow you across browser sessions. Export first, then clear freely.

What Is MIDI Recorder? A Browser-Based MIDI Recording Tool

MIDI Recorder (midi-recorder.web.app) is a free browser tool that records MIDI input from a connected MIDI keyboard and lets you export the performance as a MIDI file. It requires no installation and no account — you open the page, plug in a MIDI keyboard, and play. It works only if JavaScript is enabled and your browser supports MIDI access (Chrome is recommended; other browsers may need the Jazz-Soft Web MIDI API extension).

What MIDI Recorder does

The tool covers a deliberately narrow job: capturing live MIDI performance and saving it as a file.

  • Records MIDI input from a connected device in real time.
  • Exports a MIDI file via a "Save MIDI File" action.
  • Handles multiple takes with Clear, Undo, and a "Recover Recordings" option, so an accidental clear isn't necessarily final.
  • Includes a Demo mode, useful for checking that the interface works before your hardware does.

What it does not do, based on the page: there's no mention of audio recording, notation, editing, or multi-track arrangement. It is a recorder, not a DAW.

Requirements and setup

Requirement Detail
JavaScript Must be enabled — the app will not load without it
Browser MIDI support Chrome is the suggested option; other browsers may need the Jazz-Soft Web MIDI API extension
MIDI device A MIDI keyboard (or other MIDI controller) plugged in and powered on
Account / install None indicated

How to record and export

  1. Open the page in a MIDI-capable browser. The Input section shows a "MIDI devices" list that loads your connected hardware.
  2. Confirm your device appears in that list. If it doesn't, the page itself suggests: check the keyboard is plugged in and switched on, refresh the page, unplug and replug the device, or restart your computer.
  3. Play your keyboard. Notes are captured as you perform.
  4. Export when finished using "Save MIDI File." If nothing was captured, the app reports "No notes recorded" rather than producing an empty file.
  5. Correct mistakes with Undo, or Clear followed by Recover Recordings if you cleared by accident.

Common problems and what to try

  • "No MIDI devices detected" — the device isn't reaching the browser. Work through the page's own checklist: power, cable, refresh, replug, restart.
  • "This browser doesn't support MIDI access" — switch to Chrome, or install the Jazz-Soft Web MIDI API extension for your current browser.
  • "Failed to get MIDI access" — the browser blocked or couldn't complete the MIDI permission handshake. Retrying after a refresh, or in Chrome, is the first thing to test.
  • Nothing exports — check for the "No notes recorded" message; the export is empty because no input was captured, not because saving failed.

Who it's for

MIDI Recorder suits a quick capture: sketching an idea on a keyboard and getting a .mid file without opening a DAW or installing software. If you need editing, quantization, virtual instruments, or audio, this tool stops short of that — treat it as a fast input-to-file step, not a production environment.

Why MIDI Recorder Says "No MIDI Devices Detected" or "This Browser Doesn't Support MIDI Access"

MIDI Recorder shows "No MIDI devices detected" when the browser can reach the Web MIDI API but finds no connected device, and "This browser doesn't support MIDI access" when the browser can't reach the API at all. The first is usually a hardware or connection problem; the second is almost always a browser problem. Fix the browser case by switching to Chrome or installing the Jazz-Soft Web MIDI API extension, and fix the device case by checking the physical connection before anything else.

What each message actually means

The two errors come from different points in the startup sequence, so they point to different causes.

Message What it means First thing to try
"This browser doesn't support MIDI access" The browser has no Web MIDI API available, so the app never gets far enough to look for devices Use Chrome, or install the Jazz-Soft Web MIDI API extension
"No MIDI devices detected" The API is available, but no MIDI input device is visible to the browser Confirm the keyboard is plugged in and powered on, then refresh
"Failed to get MIDI access" The API exists but the request for access did not succeed Refresh the page, then check browser permissions

If you see the "MIDI devices: Loading..." line stuck before either message, the app is still waiting on the browser's device list — the same fixes below apply.

Fixing "This browser doesn't support MIDI access"

This message means the browser itself can't provide MIDI access. The page's own guidance is to try Chrome, or for other browsers, install the Jazz-Soft Web MIDI API extension.

  1. Open the page in Chrome first. This is the shortest path, since Chrome exposes the Web MIDI API natively.
  2. If you want to stay in another browser, install the Jazz-Soft Web MIDI API extension, then reload the page.
  3. After either change, reload MIDI Recorder and check whether the "MIDI devices" line resolves to a device name instead of the error.

Note that the app requires JavaScript to run at all. If JavaScript is disabled or blocked, you'll see the "This app requires JavaScript" notice rather than a MIDI-specific error — enable JavaScript before troubleshooting MIDI.

Fixing "No MIDI devices detected"

Here the browser is working; it just can't see a keyboard. Work through these in order, since each step is cheaper than the next.

  1. Check the physical connection. Make sure the keyboard is plugged into your computer and turned on. A keyboard that is connected but powered off will not appear.
  2. Refresh the page. The device list is read when the page loads, so a device connected afterward may not show up until you reload.
  3. Unplug and plug the device back in. This forces the operating system to re-enumerate the device, which often makes it visible to the browser again.
  4. Restart your computer. This is the last resort in the app's own guidance, and it clears cases where the device is stuck at the system level.

If the device still doesn't appear after all four steps, the problem is likely outside the browser — for example, a driver or cable issue — rather than something MIDI Recorder can fix.

Verifying it worked

Once a device is recognized, the "MIDI devices" line stops showing "Loading..." and "No MIDI devices detected" and instead lists your connected device. From there:

  • Play a few notes on the keyboard. The app's demo function lets you confirm input is arriving without recording anything permanent.
  • Use Record to capture notes, then Stop when finished.
  • Use Export → Save MIDI File to download the result. If no notes were captured, the export shows "No notes recorded" — a quick signal that input never reached the app.

If you recorded something by mistake, Clear removes it, and Undo reverses the last action. Recover Recordings restores earlier takes; when there's nothing left to restore it reports "No more recordings to recover."

Common sticking points

  • Assuming the browser is fine because it's modern. Support for the Web MIDI API varies by browser, so a current browser can still show the "doesn't support MIDI access" message. The app's own recommendation is Chrome or the Jazz-Soft extension.
  • Skipping the power check. "Plugged in" and "turned on" are separate conditions, and a powered-off keyboard produces the same "No MIDI devices detected" message as an unplugged one.
  • Not refreshing after connecting. Connecting a keyboard while the page is already open often requires a reload before it appears.
  • Confusing the two errors. If you see the support message, no amount of replugging will help — change the browser or add the extension first.
What Browser and Device Do I Need to Use MIDI Recorder?

MIDI Recorder needs three things to work: JavaScript enabled, a browser with Web MIDI access, and a MIDI input device that your computer recognizes. Chrome is the safest choice. If you use another browser, you may need the Jazz-Soft Web MIDI API extension before the app can see your keyboard.

The three requirements

Requirement Why it matters What happens if it's missing
JavaScript enabled The app itself is a script-driven page You see "This app requires JavaScript" instead of the recorder
Browser with Web MIDI access The page reads MIDI data through the Web MIDI API You see "This browser doesn't support MIDI access"
A connected MIDI input device The app records what the device sends You see "No MIDI devices detected"

All three must be satisfied at the same time. A supported browser with no keyboard plugged in still won't record anything.

Which browsers work

Chrome is the browser the app points to directly. If you're on a different browser and the app reports no MIDI support, the suggested fix is the Jazz-Soft Web MIDI API extension, which adds MIDI access to browsers that don't expose it natively.

So your practical options are:

  • Chrome — use it as-is, no extension needed.
  • Other browsers — install the Jazz-Soft Web MIDI API extension, then reload the page.

If you'd rather not install an extension, switching to Chrome is the simpler path.

What counts as a MIDI device

The app lists whatever MIDI inputs your system reports under "MIDI devices." That's typically a USB MIDI keyboard, but any device that presents itself as a MIDI input to your computer can appear there. The page loads this list dynamically, so it briefly shows "Loading..." before the devices appear.

The app's own guidance for a device that isn't showing up:

  1. Make sure it's plugged into your computer and turned on.
  2. Refresh the page.
  3. Unplug it and plug it back in.
  4. Restart your computer.

These steps address the common case where the device is physically connected but the browser hasn't picked it up.

Quick check before you start

Open the page and look at the MIDI devices list:

  • Your device is listed — you're ready to record.
  • "No MIDI devices detected" — the browser has MIDI access but sees no input; work through the plug-in/turn-on/refresh steps above.
  • "This browser doesn't support MIDI access" — the problem is the browser, not the device; switch to Chrome or add the extension.

Once a device appears, plug in your keyboard and play — the app records the notes as you go, and you can export them with "Save MIDI File."

How to Record and Save a MIDI File with MIDI Recorder

MIDI Recorder (midi-recorder.web.app) records what you play on a connected MIDI keyboard and lets you export it as a MIDI file. You need three things: a MIDI keyboard or controller, a browser with Web MIDI access (the page points to Chrome, or the Jazz-Soft Web MIDI API extension for other browsers), and JavaScript enabled. If any of those are missing, the app can't capture notes.

Before You Start

Requirement Why it matters
MIDI keyboard/controller The app records MIDI input from a device, not audio from a microphone
Chrome, or another browser with the Jazz-Soft Web MIDI API extension The page states this browser doesn't support MIDI access without it
JavaScript enabled The app itself states it requires JavaScript
Device plugged in and powered on A device that is off or unplugged won't appear in the device list

Step-by-Step: Record and Save

1. Connect your MIDI keyboard

Plug the keyboard into your computer and turn it on. The app's Input section shows a MIDI devices list; when the device is recognized, it appears there instead of the "No MIDI devices detected" message.

2. Confirm the device is detected

Look at the MIDI devices list. If your keyboard shows up, you're ready. If it doesn't, see the troubleshooting section below before playing.

3. Play to record

The page's instruction is simply: "Plug in a MIDI keyboard and play away!" Notes you play are captured as you perform. There is a Stop control to end capture, and a Demo option if you want to see the app in action first.

4. Export your recording

Use Export → Save MIDI File to download what you recorded as a MIDI file. If nothing was captured, the export area shows "No notes recorded," which means there is nothing to save yet.

5. Manage takes if needed

  • Clear removes the current recording.
  • Undo steps back.
  • Recover Recordings restores earlier takes; if there is nothing to restore, it reports "No more recordings to recover."

If Nothing Gets Recorded

Work through these checks in order — they match the guidance shown in the app:

  1. Device not showing up? Make sure it's plugged into your computer and turned on.
  2. Refresh the page. A fresh load often re-detects the device.
  3. Unplug and plug it back in. This re-establishes the MIDI connection.
  4. Restart your computer if the device still doesn't appear.
  5. Check browser support. If you see "This browser doesn't support MIDI access," switch to Chrome or install the Jazz-Soft Web MIDI API extension for your browser.
  6. Check for a MIDI access error. A "Failed to get MIDI access" message means the browser blocked or couldn't grant MIDI permission — revisit the browser/extension step.

If the device is detected and you play, but Export still says "No notes recorded," confirm you actually entered recording (not just monitoring) and that you pressed Stop before exporting.

Quick Reference

Goal Action
See if your keyboard is connected Check the MIDI devices list in the Input section
Capture a performance Play after connecting; use Stop to end
Save your take Export → Save MIDI File
Start over Clear
Undo the last change Undo
Get back an earlier take Recover Recordings

The whole workflow is: connect → confirm detection → play → stop → export. Most failures trace back to the device not being detected or the browser lacking MIDI access, so resolve those two first.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Several search or sharing settings need attention. Together they may make snippets, preview images or preferred URLs less consistent across platforms.

Domain and Registration

Registered in 2019, this domain has about 7 years of history. That suggests continuity, although ownership and purpose may have changed. The registrar, MarkMonitor Inc., specializes in corporate domain and brand management, suggesting attention to domain asset protection. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The domain uses the common .app extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by Google Cloud DNS, indicating managed DNS hosting. CAA records restrict which certificate authorities are authorized to issue certificates. No CNAME was found; the observed records resolve directly to addresses. No MX record was found. A conventional explicit inbound-mail route is not configured. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed.

TLS and Certificates

The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Google Trust Services cloud or CDN ecosystem. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, clickjacking protection. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The x-cache, x-served-by response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers. No CORS permission header was found, so browsers normally restrict cross-origin script access.

Technology Stack Analysis

The public page identifies Fastly without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

No homepage meta description was detected, leaving snippet selection more dependent on page text. No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. No Open Graph metadata was detected, so social previews may depend on platform inference. The title has 13 characters, within a common display range. The observed directives allow indexing and link following.

Hosting and Email

DNSGoogle Cloud DNS
HostingFastly
EmailUnknown
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagUnited States Inferred 199.36.158.100

Registration details

RDAP / WHOIS

RegistrarMarkMonitor Inc.
Registered2019-01-08
Expires2027-01-08
Domain statusclient delete prohibited、client transfer prohibited、client update prohibited
Nameserversns1.googledomains.com、ns2.googledomains.com、ns3.googledomains.com、ns4.googledomains.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Amidi-recorder.web.app199.36.158.10086400—
AAAAmidi-recorder.web.app2620:0:890::10086400—
NSweb.appns1.googledomains.com12787—
NSweb.appns2.googledomains.com12787—
NSweb.appns3.googledomains.com12787—
NSweb.appns4.googledomains.com12787—
CAAweb.app0 issue "pki.goog"86400—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectweb.app
IssuerGoogle Trust Services
Valid until2026-12-22T17:59 · Remaining when checked: 78 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
cache-controlmax-age=3600
strict-transport-securitymax-age=31556926; includeSubDomains; preload

Identified technologies

Fastly

Pages, Search and Sharing

Meta descriptionNot detected
Canonical URLNot detected
LanguageEnglish (default)
Twitter CardNot detected

Unknown

No robots.txt found

No sitemaps found

User reviews (0)

  • No reviews yet.