Skip to content
https://firebase.google.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
98
GRADE
A+
FIX
1
REVIEW
1
PASS
7
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
7 PASS 1 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
6 A records, 27 ms lookup
PASS
6 A records, 27 ms lookup
Info::
Resolves to 6 IPv4 address(es)
Got: 142.251.16.139, 142.251.16.102, 142.251.16.138, 142.251.16.100, 142.251.16.113, 142.251.16.101
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2607:f8b0:4004:c17::71, 2607:f8b0:4004:c17::64, 2607:f8b0:4004:c17::8a, 2607:f8b0:4004:c17::66
Info::
No NS records found
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: 27 ms
Got: 27 ms
A142.251.16.139, 142.251.16.102, 142.251.16.138, 142.251.16.100, 142.251.16.113, 142.251.16.101
AAAA2607:f8b0:4004:c17::71, 2607:f8b0:4004:c17::64, 2607:f8b0:4004:c17::8a, 2607:f8b0:4004:c17::66
CNAME
NS
MX
TXT
google-site-verification=9_jVh7qzUYXq3S0akzHGtfrSW7Wey7Ozgxl6fW25XhE
google-site-verification=uhwfsXQVQ--QiBhn8bpFFNBy58somojecKI9wifWoqE
CAALookup not available with standard resolver
Resolved in 27 ms

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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://firebase.google.com

https://firebase.google.com

220 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://firebase.google.com200220 msHTTP/1.1Google Frontend
A+
IPv6 Readiness
IPv6 reachable (8 ms)
PASS
IPv6 reachable (8 ms)
Info::
IPv6 is configured and reachable at 2607:f8b0:4004:c17::71, 2607:f8b0:4004:c17::64, 2607:f8b0:4004:c17::8a, 2607:f8b0:4004:c17::66
Got: 8 ms connect
IPv6 Ready
AAAA Records 2607:f8b0:4004:c17::71, 2607:f8b0:4004:c17::64, 2607:f8b0:4004:c17::8a, 2607:f8b0:4004:c17::66 Connection Reachable (8 ms)
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 82 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 82 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /byptwd/
Sitemap: https://firebase.google.com/sitemap.xml

sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.firebase.google.com/
200https://firebase.google.com/

HTTP → HTTPS

301http://firebase.google.com/ https://firebase.google.com/

Consistent

A+
Domain Intelligence
google.com — via MarkMonitor Inc., 28 years, 11 months old
PASS
google.com — via MarkMonitor Inc., 28 years, 11 months old
Info::
Domain registered until Sep 14, 2028 (2 years, 5 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Domain expiry

759 days

September 14, 2028

SSL certificate

64 days

Issued by Google Trust Services

Domain age

28 years, 11 months

Registered September 15, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2607:f8b0:4004:c07::8a

Registrar

MarkMonitor Inc.

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar MarkMonitor Inc.
Created September 15, 1997 (28 years, 11 months ago)
Expires September 14, 2028 (2 years, 5 months)
Last Updated September 9, 2019
Name Servers ns1.google.com, ns2.google.com, ns3.google.com, ns4.google.com
DNSSEC Not enabled
Hosting
IP Address 2607:f8b0:4004:c07::8a
Data source: rdap (0.1s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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

Connection waterfall

DNS Lookup 11 ms TCP Connect 7 ms TLS Handshake 12 ms Server Processing 388 ms Content Transfer 24 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback