Skip to content
https://mbc.net

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
11
PASS
6
INFO
0
Probed from New York, United Stated
302 Found
Checks
17
6 PASS 11 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
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.
B
Reverse DNS
0/3 IPs match cert SAN
REVIEW
0/3 IPs match cert SAN
Info::
PTR for 54.80.133.239 does not match any cert SAN: ec2-54-80-133-239.compute-1.amazonaws.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.
Info::
PTR for 54.173.88.84 does not match any cert SAN: ec2-54-173-88-84.compute-1.amazonaws.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.
Info::
PTR for 100.50.54.99 does not match any cert SAN: ec2-100-50-54-99.compute-1.amazonaws.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
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
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.

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect is not permanent
Got: HTTP 302 Expected: 301 or 308 permanent redirect

www / non-www

200https://www.mbc.net/
200https://mbc.net/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://mbc.net/ → https://mbc.net:443/

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

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

Certificate validity

170
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
C
CDN & Delivery
Action
Assets on AWS CloudFront (host www.mbc.net, 17 assets); document served directly from origin (AWS)
REVIEW
Assets on AWS CloudFront (host www.mbc.net, 17 assets); document served directly from origin (AWS)
Warning::
Document not behind existing CDN (AWS CloudFront serves the assets)
The page's subresources are delivered by AWS CloudFront (www.mbc.net, 17 assets), but the HTML document itself comes straight from the origin (AWS). Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: delegation d1qg9orvmxh0wq.cloudfront.net
Info::
Assets on AWS CloudFront: www.mbc.net (assets: 17), cache Hit from cloudfront
Got: delegation d1qg9orvmxh0wq.cloudfront.net
Warning: Assets on a CDN, document is not: AWS CloudFront
Document origin AWS

Asset hosts on a CDN

  • www.mbc.net — AWS CloudFront · assets: 17 · Cache Status: Hit from cloudfront

Other asset hosts

  • mbc-lite-strapi-s3-backup.s3.us-east-1.amazonaws.com — assets: 28 · AWS
  • securepubads.g.doubleclick.net — assets: 2 · below probe threshold
  • www.googletagmanager.com — assets: 2 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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.
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
3 A records, 82 ms lookup
PASS
3 A records, 82 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 54.80.133.239, 54.173.88.84, 100.50.54.99
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1303.awsdns-34.org, ns-1983.awsdns-55.co.uk, ns-377.awsdns-47.com, ns-856.awsdns-43.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 82 ms
Got: 82 ms
A54.80.133.239, 54.173.88.84, 100.50.54.99
AAAA—
CNAME—
NSns-1303.awsdns-34.org, ns-1983.awsdns-55.co.uk, ns-377.awsdns-47.com, ns-856.awsdns-43.net
MX
10 mbc-net.mail.protection.outlook.com
TXT
2NF7gwzy=95567c9e40c8b7e73be70f617b011581
2je8123ucdresshat9tegmbeib
5APoXYmvcGPB/hSyIBH8zZiDfshbm1zcLasCa8c0glFBUaXOUe0eR9FqbBma8ckuuFHD+WbQ+ht04LOh...
76apac0eef1jaqer6rvv091mjr
8315-7939-6AB8-DD71-E3FA-E182-791B-0172
D934-D00D-42FB-6BD4-A8D2-3E49-8FFE-74FE
Dynatrace-site-verification=034b4034-8394-4580-8e9a-1cf909dafe0e__cull2d2si3gd3d...
MS=ms77995588
_globalsign-domain-verification=nAFEJvK9GgplzHknWaZofxfLPVM5dabx8b50HOM_A3
anthropic-domain-verification-wjfe33=U7sQPeV9S4js6EHgVrfA09cML
atlassian-domain-verification=N74x1BcgVEPz1YoNVRsYVmD/vnZk6dNSm7h2TTLBLWhJV0efj8...
bks8124q3o0a0j3pcu3i4aetq7
bw=ouSLP1R22qiUufkeR6YWQl764YGBtJXvAReMhTepyqzx
ca3-0af3253b0fa9490d96c439ba1786585b
ca3-173104258765483e934725be68568057
ca3-d4d9ca9b30944370a66d8ca9d7ad6802
d365mktkey=Y2llv4iZmEPpbXY3JepKHLA6QBwij8LrIP1oKhXpnHwx
dmVxg4Dm6cTM/D582bxbbpXOp1KHWMbNlsauuFLgI23uk+ufnRHzGOOm2RSRsA8Xyq3K/npqcr03/vba...
edisen-verification-key=f4aeedad-eb08-4846-a713-aea02e05370f
facebook-domain-verification=msebemu8qnhnccejvcrcbukjrqsoyt
fbq16crmu4hbqmkkm40ejsl0ug
google-site-verification=4be51Te8tMYp_d5OtUhT3PoPoKjYXsd0ZUdUj7JfdTs
google-site-verification=625RdBVC8wqFIyAg_V8IHGC_RXRjb4qXPD1_FbBrVuk
google-site-verification=6ZZSYcRrAF697-IIqVXaFkcUgmJhBcf6s3aUhHvfynw
google-site-verification=EMJn4BxNOAFKVJw8mjkqSGWrtXS2Fs2hjUM4rjwuuLM
google-site-verification=tNibWwXQenjnScL7niPGZLE2A00yqnsReGLPxEhAamA
google-site-verification=vIQjO5U67vUvJ8-r5mvNJ5OErv_VjkA_xy6o1x9a5uE
miro-verification=0723660e7bcfc3b7f8997fa406185ca60ce7ffde
mongodb-site-verification=k5R7sx3HZqFkiyEZk875Xt6XuYAO02Mf
ms-domain-verification=27fb68d1-3293-4554-9057-f9d2570a57ca
openai-domain-verification=dv-FG2zwM7lyXq9EGvGyeLkj28T
smartsheet-site-validation=sRKU4I1ofVlB5YotbCXipcwzYJLZn0Wr
SPF v=spf1 redirect=bcii6y0h._spf._d.mim.ec
w2SYb7LL7wzbYlysZl56dnZgSZsYktxQiriSu0sBtVA=
zapier-domain-verification-challenge=1a676642-f927-407a-b200-faa83828e427
CAALookup not available with standard resolver
Resolved in 82 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 7ms across 3 resolvers (spread 10ms)
PASS
Mean 7ms across 3 resolvers (spread 10ms)
Info::
Quad9: 4ms
Got: 4ms via 9.9.9.9:53
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Google: 14ms
Got: 14ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 60 ms total
PASS
1 redirect(s), 60 ms total
Info::
Single redirect
Got: https://mbc.net → https://www.mbc.net:443/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://mbc.net

https://mbc.net

29 ms · HTTP/1.1

302

https://www.mbc.net:443/

31 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mbc.net30229 msHTTP/1.1awselb/2.0
2https://www.mbc.net:443/20031 msHTTP/1.1nginx

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+
Domain Intelligence
mbc.net — via Register.com - Network Solutions, LLC, 25 years, 7 months old, hosted on AWS
PASS
mbc.net — via Register.com - Network Solutions, LLC, 25 years, 7 months old, hosted on AWS
Info::
Domain registered until Jul 16, 2032 (5 years, 9 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Register.com - Network Solutions, LLC
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: AWS
Got: AS14618
Domain expiry

2097 days

July 16, 2032

SSL certificate

170 days

Issued by GoDaddy.com

Domain age

25 years, 7 months

Registered July 16, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

54.173.88.84

Registrar

Register.com - Network Solutions, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Register.com - Network Solutions, LLC
Created July 16, 2001 (25 years, 7 months ago)
Expires July 16, 2032 (5 years, 9 months)
Last Updated July 17, 2022
Name Servers ns-1303.awsdns-34.org, ns-1983.awsdns-55.co.uk
DNSSEC Not enabled
Hosting
IP Address 54.173.88.84
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.6s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 34 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
10 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
6 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
11 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
34 ms
Total Time Total request time from DNS lookup through full response.
34 ms

Connection waterfall

DNS Lookup 10 ms TCP Connect 6 ms TLS Handshake 11 ms Server Processing 7 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback