Infrastructure - https://idc.com 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.

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

URL Variants

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

REVIEW

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

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.idc.com/

200https://idc.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://idc.com/ → https://idc.com/

Consistent

B

TLS Certificate Expiry & Recommendations

89 days until leaf cert expires — 5 issues to address

REVIEW

Certificate validity

89

days left

0d 30d 60d 90d+

Recommended actions

Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
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

A+

DNS Records

1 A records, 61 ms lookup

PASS

1 A records, 61 ms lookup

Resolves to 1 IPv4 address(es)

Got: 192.0.66.129

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns-1821.awsdns-35.co.uk, ns-1486.awsdns-57.org, ns-376.awsdns-47.com, ns-1020.awsdns-63.net

1 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 61 ms

Got: 61 ms

A	192.0.66.129
AAAA	—
CNAME	—
NS	ns-1821.awsdns-35.co.uk, ns-1486.awsdns-57.org, ns-376.awsdns-47.com, ns-1020.awsdns-63.net
MX	10 idc-com.mail.protection.outlook.com
TXT	mgverify=b3837f3d533795011bda74e0818813b43e19fed5e39c278be93b1fe599fb71eb SFMC-BkzH9VL9Wt6Qd_tbGKho6ZP2bIGwvdlI3kgmnBs2 box-domain-verification=7a4cee98fda1d82847b097b0ff46969d8857a92ccfdc15719deb4fd3... slack-domain-verification=C4khAQa9sYT4K73ZDAXAYciBaEGIGFH6hI6536l0 anthropic-domain-verification-7nrbq8=LPJWTuGmCDPlFX2Zjsn2hTCBE docusign=588df1b5-9825-42f1-aa93-1ea221867bf5 beautifulai-site-verification=d664beb1-10fb-4783-a4c0-7fa8bc7b711c google-site-verification=rkkScVsMpuqXatGMagMm159evJOXO3CrWnXxU0DsG28 perplexity-ai-domain-verification-146h1k=phkgputFr9GQMCEmeWGLMf8HH wrike-verification=MzEyODc4OmUzYzdiNDRiMzg1ZDNkYjdmYjdiOTJiODNkOWU1OWRiM2ViM2UxO... openai-domain-verification=dv-vavK03qneGObYLq086JMkK6c atlassian-domain-verification=OgMkscBLxaedWxvOpudpOs7V8IcoptPHKVsL32r4xvdDyzMF/l... onetrust-domain-verification=cc0345893aad4f9fa7dbb40bff8ad0dc 6d6e8b5f-2b19-4b0a-879e-7b75340203ce google-site-verification=5HbooOhirDDTpivEEuweJetr8AuF_GsZZkCSSFSiF5Q SFMC-ZFYEN_-E3lDIaXrj6Y2gpU3J1Xm76V9Oh-n_l9qC figma-domain-verification=fc832aaeb526a5845ac439dbf4a77f216f8a3967f779d4bc6d56cf... canva-site-verification=yg-xWt0H-iqD9zuT2J5ycw parallels-domain-verification=b80c33e26dac4463bbbdef5dc81e20e3ef76ff607b19435798... SPF v=spf1 include:_u.idc.com._spf.dmarcly.com include:spf.protection.outlook.com in... pexip-ms-tenant-domain-verification=5cc89ccd-1cc1-4485-bf6d-48aa384d1660 jamf-site-verification=sW5qhhYD7Pb4HTn4soz2Tw sprout-social-ec573070-635f-40fc-b268-c020787bb1c6 adobe-idp-site-verification=6d8e5080b896d3b561b273ab5de1b361e5c95cded1a01d6ac20b... pendo-domain-verification=tJolXCg5xU5O1VXgXATA6vaXDCI knowbe4-site-verification=d3f99773308e74aca24e3c867c088358 SFMC-lYr49ziWZVySzut0bDqdNj4_cM4kps0hJimYmdPy
CAA	Lookup not available with standard resolver

Resolved in 61 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A

Redirect Chain

1 redirect(s), 40 ms total

PASS

1 redirect(s), 40 ms total

Single redirect

Got: https://idc.com → https://www.idc.com/ (301)

WWW normalization redirect

https://idc.com

5 ms · HTTP/1.1

301

https://www.idc.com/

34 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://idc.com	301	5 ms	HTTP/1.1	nginx
2	https://www.idc.com/	200	34 ms	HTTP/1.1	nginx

See the visual redirect chain in the HTTP Probe tab →

A+

Crawlability

robots.txt present, sitemap with 28 URLs

PASS

robots.txt present, sitemap with 28 URLs

robots.txt is present

Got: 169 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 28 entries

Sitemap index with 28 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 169 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://www.idc.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK

sitemap.xml 200 OK

Type Sitemap Index URLs 28 entries Valid XML Yes

Child Sitemaps:

A

Domain Intelligence

idc.com — via MarkMonitor Inc., 29 years, 2 months old, hosted on WordPress.com (Automattic)

PASS

idc.com — via MarkMonitor Inc., 29 years, 2 months old, hosted on WordPress.com (Automattic)

Domain expires in 76 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Jul 7, 2026

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.

Registrar: MarkMonitor Inc.

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.

Hosting: WordPress.com (Automattic)

Got: AS2635

Domain expiry

21 days

July 7, 2026

SSL certificate

89 days

Issued by Let's Encrypt

Domain age

29 years, 2 months

Registered July 8, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.129

Registrar

MarkMonitor Inc.

Unlocked 4 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the domain or enable auto-renewal to prevent accidental expiry
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar MarkMonitor Inc.

Created July 8, 1997 (29 years, 2 months ago)

Expires July 7, 2026 (2 months)

Last Updated June 5, 2025

Name Servers ns-1020.awsdns-63.net, ns-1486.awsdns-57.org, ns-1821.awsdns-35.co.uk, ns-376.awsdns-47.com

DNSSEC Not enabled

Hosting

IP Address 192.0.66.129

ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)

Provider WordPress.com (Automattic)

Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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 597 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

37 ms

TCP Connect

0 ms

TLS Handshake

3 ms

Time to First Byte

597 ms

Total Time

598 ms

Connection waterfall

DNS Lookup 37 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 557 ms Content Transfer 0 ms