Infrastructure - https://portal.itb.com.sa BeaverCheck Audit

D

CDN & Delivery

Action

No CDN detected

FIX

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

DNS Records

1 A records, 391 ms lookup

REVIEW

1 A records, 391 ms lookup

Resolves to 1 IPv4 address(es)

Got: 70.39.64.194

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution is slow (391 ms)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Got: 391 ms

A	70.39.64.194
AAAA	—
CNAME	—
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 391 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)

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)

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.

B

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 70.39.64.194 does not match any cert SAN: e1.buynowgou.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

C

Multi-Resolver DNS Speed

Action

Mean 229ms across 3 resolvers (spread 228ms)

REVIEW

Mean 229ms across 3 resolvers (spread 228ms)

Cloudflare: 151ms

Got: 151ms via 1.1.1.1:53

Google: 157ms

Got: 157ms via 8.8.8.8:53

Quad9: 379ms

Got: 379ms via 9.9.9.9:53

High latency spread between resolvers: 228ms (min 151ms / max 379ms)

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.

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

Crawlability

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

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

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

44 days until leaf cert expires — 2 issues to address

REVIEW

Certificate validity

44

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

B

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

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

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

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+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A

Redirect Chain

1 redirect(s), 654 ms total

PASS

1 redirect(s), 654 ms total

Single redirect

Got: https://portal.itb.com.sa → https://login.microsoftonline.com/69f03718-34c4-4b6a-8e15-1a18c39e5c14/oauth2/authorize?client_id=c238299c-020d-4d04-9925-61c729f8b2fa&response_type=code%20id_token&scope=openid%20profile&state=OpenIdConnect.AuthenticationProperties%3Do5F8Ls0TMcztgMc4rtt87Zz_RVwxrVr6Na2IRik-R1hAD-94F3qtf4vI6AsU32Ftnj-rDcx9jVnro-8e2GweCflapR5sveDkFbMZg7Jeu6VrnNK9SdaOhMScRarWTtZw&response_mode=form_post&nonce=639227191950548684.ZmI0M2FjZmMtYmY1Ny00OGM1LTkxNWYtYjUyMjAyZWVkNTk0MjU5ZTE0NmUtYjc1YS00Y2VhLThlNDAtYzYxNTA4Y2YxZDhm&x-client-SKU=ID_NET472&x-client-ver=8.16.0.0 (302)

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://portal.itb.com.sa

Redirect overhead: 654 ms total

Got: 654 ms

Cross-domain redirect detected

https://portal.itb.com.sa

382 ms · HTTP/1.1

302

https://login.microsoftonline.com/69f037...

271 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://portal.itb.com.sa	302	382 ms	HTTP/1.1
2	https://login.microsoftonline.com/69f037...	200	271 ms	HTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

HTTP→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

https://www.portal.itb.com.sa/

200https://portal.itb.com.sa/

HTTP → HTTPS

302http://portal.itb.com.sa/ → https://login.microsoftonline.com/69f03718-34c4-4b6a-8e15-1a18c39e5c14/oauth2/authorize?client_id=c238299c-020d-4d04-9925-61c729f8b2fa&response_type=code%20id_token&scope=openid%20profile&state=OpenIdConnect.AuthenticationProperties%3D285cWheEkWtGcqYZnM7_3MLqxwP-pwf-FOadZ3iTcGHcg1tdE6rlgMXRC3shjQSlD_wopYnxddZNNqHM6LpMtYUs0K5xz5E4cx3j13WlT9ftxx4AJShsaB9Ze8RHo0ms&response_mode=form_post&nonce=639227191982425170.MDBkNGRjYzctYmQ0ZC00NGQzLTg1NGEtNGI5ZGE5NTVlNjdlNTdkNjA2MzYtM2ExNy00NWQwLTkxYWQtNmQ1ODg0YWEwYjZh&x-client-SKU=ID_NET472&x-client-ver=8.16.0.0

Use a permanent redirect (301 or 308) instead of a temporary one

A+

Domain Intelligence

itb.com.sa — hosted on SHARKTECH - Sharktech, US

PASS

itb.com.sa — hosted on SHARKTECH - Sharktech, US

Hosting: SHARKTECH - Sharktech, US

Got: AS46844

Domain expiry

Unknown

SSL certificate

44 days

Issued by Sectigo Limited

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

SHARKTECH - Sharktech, US

ASN AS46844

70.39.64.194

Registrar

Registrar unknown

Lock status unknown 2 NS records

Expiry timeline

Today

+1 year

SSL expiry Danger zone (≤30 days)

Registrar

Name Servers ns1.dnetns.com, ns2.dnetns.com

Hosting

IP Address 70.39.64.194

ASN AS46844 (SHARKTECH - Sharktech, US)

Provider SHARKTECH - Sharktech, US

Data source: whois (2.4s)

A+

HTTP Probe Timing

Total 387 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

299 ms

TCP Connect

25 ms

TLS Handshake

33 ms

Time to First Byte

387 ms

Total Time

388 ms

Connection waterfall

DNS Lookup 299 ms TCP Connect 25 ms TLS Handshake 33 ms Server Processing 30 ms Content Transfer 0 ms