Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DMulti-Resolver DNS SpeedActionMean 586ms across 3 resolvers (spread 906ms)FIX
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/1 IPs match cert SANREVIEW
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations77 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
BOperational Status PageNo status page link detectedREVIEW
ADNS Records1 A records, 385 ms lookupPASS
| A | 199.36.158.100 |
| AAAA | — |
| CNAME | — |
| NS | ns3.ict.omantel.om, ns4.ict.omantel.om |
| MX | 0 safaqat-om.mail.protection.outlook.com |
| TXT | SPF v=spf1 include:spf.protection.outlook.com include:mxsspf.sendpulse.com -all SPF v=spf1 include:spf.protection.outlook.com -all hosting-site=safaqat-website SPF v=spf1 include:spf.protection.outlook.com ~all google-site-verification=bN8z6LysmVDm_6UwL23l8ks3RdK4nSYDq6JtaPRyY-c |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Redirect ChainNo redirects — direct accessPASS
https://SafaQat.om
8 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://SafaQat.om | 200 | 8 ms | HTTP/1.1 |
A+Crawlabilityrobots.txt present, sitemap with 28 URLsPASS
User-agent: *
Allow: /
Disallow: /admin/
Disallow: /api/
Sitemap: https://safaqat.om/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain IntelligenceSafaQat.om — via Oman Telecommunication Company (Omantel), hosted on FastlyPASS
Unknown
77 days
Issued by Google Trust Services
Unknown
Status unknown
Protects against DNS spoofing
Fastly
ASN AS54113
199.36.158.100
Oman Telecommunication Company (Omantel)