Skip to content
https://tender.safaqat.om

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
2
REVIEW
8
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 8 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 505ms across 3 resolvers (spread 927ms)
FIX
Mean 505ms across 3 resolvers (spread 927ms)
Info::
Google: 142ms
Got: 142ms via 8.8.8.8:53
Info::
Quad9: 305ms
Got: 305ms via 9.9.9.9:53
Info::
Cloudflare: 1069ms
Got: 1069ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 927ms (min 142ms / max 1069ms)
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.
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
Got: document origin: DigitalOcean
No CDN (document or assets)
Document origin DigitalOcean

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

B
DNS Records
1 A records, 381 ms lookup
REVIEW
1 A records, 381 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 209.38.251.14
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
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'.
Warning::
DNS resolution is slow (381 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 381 ms
A209.38.251.14
AAAA—
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 381 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

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)

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

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 209.38.251.14: lookup 209.38.251.14: 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
71 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
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.
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://tender.safaqat.om

https://tender.safaqat.om

131 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tender.safaqat.om200131 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 18 URLs
PASS
robots.txt present, sitemap with 18 URLs
Info::
robots.txt is present
Got: 168 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 18 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 168 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /user/
Disallow: /auth/
Disallow: /otp
Disallow: /forgot-password
Disallow: /verify-cr

Sitemap: https://tender.safaqat.om/sitemap.xml

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

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

HTTP → HTTPS

301http://tender.safaqat.om/ → https://tender.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

71 days

Issued by Let's Encrypt

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.1s)
A+
HTTP Probe Timing
Total 242 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
150 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
30 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
33 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
241 ms
Total Time Total request time from DNS lookup through full response.
242 ms

Connection waterfall

DNS Lookup 150 ms TCP Connect 30 ms TLS Handshake 33 ms Server Processing 29 ms Content Transfer 1 ms
A+
Health Check Endpoint
Health endpoint at https://tender.safaqat.om/health (HTTP 200)
PASS
Health endpoint at https://tender.safaqat.om/health (HTTP 200)
Info::
Public health endpoint at https://tender.safaqat.om/health
Got: https://tender.safaqat.om/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback