Skip to content
https://safaqat.om

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 7 REVIEW 1 FIX
D
Multi-Resolver DNS Speed
Action
Mean 263ms across 3 resolvers (spread 333ms)
FIX
Mean 263ms across 3 resolvers (spread 333ms)
Info::
Google: 135ms
Got: 135ms via 8.8.8.8:53
Info::
Cloudflare: 187ms
Got: 187ms via 1.1.1.1:53
Info::
Quad9: 468ms
Got: 468ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 333ms (min 135ms / max 468ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
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
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 199.36.158.100: lookup 199.36.158.100: 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.
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
TLS Certificate Expiry & Recommendations
81 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

81
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 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
1 A records, 400 ms lookup
PASS
1 A records, 400 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 199.36.158.100
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns4.ict.omantel.om, ns3.ict.omantel.om
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (400 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 400 ms
A199.36.158.100
AAAA—
CNAME—
NSns4.ict.omantel.om, ns3.ict.omantel.om
MX
0 safaqat-om.mail.protection.outlook.com
TXT
google-site-verification=bN8z6LysmVDm_6UwL23l8ks3RdK4nSYDq6JtaPRyY-c
SPF v=spf1 include:spf.protection.outlook.com include:mxsspf.sendpulse.com -all
SPF v=spf1 include:spf.protection.outlook.com -all
SPF v=spf1 include:spf.protection.outlook.com ~all
hosting-site=safaqat-website
CAALookup not available with standard resolver
Resolved in 400 ms

Multiple A records provide failover if one server goes down.

Why this matters

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.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://safaqat.om

https://safaqat.om

63 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://safaqat.om20063 msHTTP/1.1
A+
Crawlability
robots.txt present, sitemap with 24 URLs
PASS
robots.txt present, sitemap with 24 URLs
Info::
robots.txt is present
Got: 104 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 24 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 104 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Allow: /

Disallow: /admin/

Disallow: /api/


Sitemap: https://safaqat.om/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: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.safaqat.om/
200https://safaqat.om/

Preferred variant: non-www

HTTP → HTTPS

301http://safaqat.om/ → https://safaqat.om/

Consistent

A+
Domain Intelligence
safaqat.om — via Oman Telecommunication Company (Omantel), hosted on Fastly
PASS
safaqat.om — via Oman Telecommunication Company (Omantel), hosted on Fastly
Info::
Registrar: Oman Telecommunication Company (Omantel)
Info::
Hosting: Fastly
Got: AS54113
Domain expiry

Unknown

SSL certificate

81 days

Issued by Google Trust Services

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

199.36.158.100

Registrar

Oman Telecommunication Company (Omantel)

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Registrar Oman Telecommunication Company (Omantel)
Name Servers ns4.ict.omantel.om, ns3.ict.omantel.om
Registrant Egad Technology
Hosting
IP Address 199.36.158.100
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: whois (1.0s)
A
HTTP Probe Timing
Total 447 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
250 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
446 ms
Total Time Total request time from DNS lookup through full response.
448 ms

Connection waterfall

DNS Lookup 250 ms TCP Connect 0 ms TLS Handshake 5 ms Server Processing 191 ms Content Transfer 1 ms
A
CDN & Delivery
Fastly (MISS)
PASS
Fastly (MISS)
Info::
Document is served via Fastly CDN (edge: TOJ)
Got: x-served-by: cache-toj-leto2350064-TOJ
Info::
CDN cache status: MISS
Document served via CDN: Fastly
Provider Fastly Cache Status MISS Evidence x-served-by: cache-toj-leto2350064-TOJ
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 3 header(s)
Got: x-cache=MISS, x-cache-hits=0, x-served-by=cache-toj-leto2350064-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback