Skip to content
https://www.mmhmm.app

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 5 REVIEW
B
Redirect Chain
2 redirect(s), 510 ms total
REVIEW
2 redirect(s), 510 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
Redirect overhead: 510 ms total
Got: 510 ms
Info::
Cross-domain redirect detected

https://www.mmhmm.app

67 ms · HTTP/1.1

301

https://www.airtime.com/

235 ms · HTTP/1.1

307

https://www.airtime.com/home

209 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.mmhmm.app30167 msHTTP/1.1Vercel
2https://www.airtime.com/307235 msHTTP/1.1Vercel
3https://www.airtime.com/home200209 msHTTP/1.1Vercel

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Domain Intelligence
mmhmm.app — via Squarespace Domains II LLC., 6 years old, hosted on AWS
REVIEW
mmhmm.app — via Squarespace Domains II LLC., 6 years old, hosted on AWS
Critical::
Domain expires in 18 days
This domain expires on April 26, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires Apr 26, 2026
Info::
DNSSEC is enabled
Info::
Registrar: Squarespace Domains II LLC.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

EXPIRED

April 26, 2026

SSL certificate

46 days

Issued by Let's Encrypt

Domain age

6 years

Registered April 26, 2020

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

76.76.21.21

Registrar

Squarespace Domains II LLC.

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
Registrar Squarespace Domains II LLC.
Created April 26, 2020 (6 years ago)
Expires April 26, 2026 (18 days)
Last Updated November 26, 2025
Name Servers ns-1278.awsdns-31.org, ns-1882.awsdns-43.co.uk, ns-344.awsdns-43.com, ns-813.awsdns-37.net
DNSSEC Enabled
Hosting
IP Address 76.76.21.21
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

This domain expires on April 26, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

B
TLS Certificate Expiry & Recommendations
46 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

46
days left
0d 30d 60d 90d+

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Vercel
REVIEW
Vercel
Info::
Site is served via Vercel CDN
Got: x-vercel-id: cdg1::rbg42-1775594460935-3a60f9a0c0e4
CDN Detected: Vercel
Provider Vercel Evidence x-vercel-id: cdg1::rbg42-1775594460935-3a60f9a0c0e4
A
DNS Records
2 A records, 21 ms lookup
PASS
2 A records, 21 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 76.76.21.142, 66.33.60.66
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: cname.vercel-dns.com
Info::
4 nameserver(s) configured
Got: ns3.vercel-dns-3.com, ns1.vercel-dns-3.com, ns4.vercel-dns-3.com, ns2.vercel-dns-3.com
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 21 ms
Got: 21 ms
A76.76.21.142, 66.33.60.66
AAAA
CNAMEcname.vercel-dns.com
NSns3.vercel-dns-3.com, ns1.vercel-dns-3.com, ns4.vercel-dns-3.com, ns2.vercel-dns-3.com
MX
TXT
CAALookup not available with standard resolver
Resolved in 21 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Crawlability
robots.txt present, sitemap with 210 URLs
PASS
robots.txt present, sitemap with 210 URLs
Info::
robots.txt is present
Got: 85 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 210 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 85 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /
Disallow: /cms/

Sitemap: https://www.airtime.com/sitemap.xml

A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.mmhmm.app/
301https://mmhmm.app/

Preferred variant: www

HTTP → HTTPS

308http://www.mmhmm.app/ https://www.mmhmm.app/

Use 301 (permanent) instead of 302 (temporary)

A+
HTTP Probe Timing
Total 137 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
60 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
44 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
138 ms
Total Time Total request time from DNS lookup through full response.
138 ms

Connection waterfall

DNS Lookup 60 ms TCP Connect 1 ms TLS Handshake 44 ms Server Processing 33 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback