Skip to content
https://abdalrhmansaid.github.io/my-website

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
5
PASS
11
INFO
1
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
17
11 PASS 5 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A
DNS Records
4 A records, 16 ms lookup
PASS
4 A records, 16 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 185.199.110.153, 185.199.111.153, 185.199.109.153, 185.199.108.153
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2606:50c0:8000::153, 2606:50c0:8001::153, 2606:50c0:8002::153, 2606:50c0:8003::153
Info::
No NS records found
Info::
No MX records — email not configured via DNS
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: 16 ms
Got: 16 ms
A185.199.110.153, 185.199.111.153, 185.199.109.153, 185.199.108.153
AAAA2606:50c0:8000::153, 2606:50c0:8001::153, 2606:50c0:8002::153, 2606:50c0:8003::153
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 16 ms

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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
CAA Records
issue: digicert.com, letsencrypt.org, sectigo.com | issuewild: digicert.com, letsencrypt.org, sectigo.com
PASS
issue: digicert.com, letsencrypt.org, sectigo.com | issuewild: digicert.com, letsencrypt.org, sectigo.com
Info::
CAA issue tag present — authorized CA(s): digicert.com, letsencrypt.org, sectigo.com
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A
Reverse DNS
4/8 IPs match cert SAN
PASS
4/8 IPs match cert SAN
Info::
PTR for 185.199.110.153 matches certificate SAN: cdn-185-199-110-153.github.com
Info::
PTR for 185.199.111.153 matches certificate SAN: cdn-185-199-111-153.github.com
Info::
PTR for 185.199.109.153 matches certificate SAN: cdn-185-199-109-153.github.com
Info::
PTR for 185.199.108.153 matches certificate SAN: cdn-185-199-108-153.github.com
Info::
PTR lookup failed for 2606:50c0:8000::153: lookup 2606:50c0:8000::153: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:50c0:8001::153: lookup 2606:50c0:8001::153: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:50c0:8002::153: lookup 2606:50c0:8002::153: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:50c0:8003::153: lookup 2606:50c0:8003::153: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
A+
Multi-Resolver DNS Speed
Mean 6ms across 3 resolvers (spread 7ms)
PASS
Mean 6ms across 3 resolvers (spread 7ms)
Info::
Quad9: 3ms
Got: 3ms via 9.9.9.9:53
Info::
Google: 7ms
Got: 7ms via 8.8.8.8:53
Info::
Cloudflare: 10ms
Got: 10ms via 1.1.1.1:53
A
Redirect Chain
1 redirect(s), 154 ms total
PASS
1 redirect(s), 154 ms total
Info::
Single redirect
Got: https://abdalrhmansaid.github.io/my-website → https://abdalrhmansaid.github.io/my-website/ (301)

https://abdalrhmansaid.github.io/my-webs...

14 ms · HTTP/1.1

301

https://abdalrhmansaid.github.io/my-webs...

140 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://abdalrhmansaid.github.io/my-webs...30114 msHTTP/1.1GitHub.com
2https://abdalrhmansaid.github.io/my-webs...200140 msHTTP/1.1GitHub.com

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:50c0:8000::153, 2606:50c0:8001::153, 2606:50c0:8002::153, 2606:50c0:8003::153
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:50c0:8000::153, 2606:50c0:8001::153, 2606:50c0:8002::153, 2606:50c0:8003::153 Connection Reachable (2 ms)
A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
Trailing slash inconsistency — both versions serve content
Got: Both with/without trailing slash return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

https://www.abdalrhmansaid.github.io/my-website
200https://abdalrhmansaid.github.io/my-website

Trailing Slash

200https://abdalrhmansaid.github.io/my-website/
200https://abdalrhmansaid.github.io/my-website

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://abdalrhmansaid.github.io/my-website → https://abdalrhmansaid.github.io/my-website

Consistent

A+
HTTP Probe Timing
Total 143 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
6 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.
6 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
143 ms
Total Time Total request time from DNS lookup through full response.
143 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 1 ms TLS Handshake 6 ms Server Processing 130 ms Content Transfer 0 ms
A
CDN & Delivery
Fastly (MISS)
PASS
Fastly (MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-gru-sbgr1930079-GRU
Info::
CDN cache status: MISS
Document served via CDN: Fastly
Provider Fastly Cache Status MISS Evidence x-served-by: cache-gru-sbgr1930079-GRU
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 4 header(s)
Got: age=0, x-cache=MISS, x-cache-hits=0, x-served-by=cache-gru-sbgr1930079-GRU
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback