Skip to content
https://socialmediatoday.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
B
TLS Certificate Expiry & Recommendations
31 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

31
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: AMS)
Got: cf-ray: 9f00055a3a170b34-AMS
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f00055a3a170b34-AMS
A+
DNS Records
2 A records, 9 ms lookup
PASS
2 A records, 9 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.39.68, 172.64.148.188
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:310a::6812:2744, 2a06:98c1:3107::ac40:94bc
Info::
2 nameserver(s) configured
Got: ivy.ns.cloudflare.com, sid.ns.cloudflare.com
Info::
4 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 9 ms
Got: 9 ms
A104.18.39.68, 172.64.148.188
AAAA2a06:98c1:310a::6812:2744, 2a06:98c1:3107::ac40:94bc
CNAME
NSivy.ns.cloudflare.com, sid.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx2.googlemail.com
TXT
JHOEj5VCQIPe4Vr+/Dq1SaDhc04wgHOiZJ3nt/mklyY=
facebook-domain-verification=r936kihf4fskxlc8xzrfqa2j3yuisl
google-site-verification=GaRd7WkrbQXFplJU7VKId-4W4YEvdRYDkZrVDvbLWAM
google-site-verification=vMpLWmR1zKkA0E1BRGU3BtUY844nnPUf9Z-fVsKXP_4
SPF v=spf1 include:_spf.google.com ~all
CAALookup not available with standard resolver
Resolved in 9 ms

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), 79 ms total
PASS
1 redirect(s), 79 ms total
Info::
Single redirect
Got: https://socialmediatoday.com → https://www.socialmediatoday.com/ (301)
Info::
WWW normalization redirect

https://socialmediatoday.com

33 ms · HTTP/1.1

301

https://www.socialmediatoday.com/

46 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://socialmediatoday.com30133 msHTTP/1.1cloudflare
2https://www.socialmediatoday.com/20046 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:310a::6812:2744, 2a06:98c1:3107::ac40:94bc
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:310a::6812:2744, 2a06:98c1:3107::ac40:94bc Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 106 URLs
PASS
robots.txt present, sitemap with 106 URLs
Info::
robots.txt is present
Got: 4954 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 106 entries
Info::
Sitemap index with 106 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 4954 B Sitemaps referenced 0 User-agents *, PetalBot, sentibot, omgilibot, omgili, facebookexternalhit/1.1, AhrefsBot, amazon-kendra # Amazon Kendra Web Crawler, Twitterbot, Googlebot-News, Googlebot-Image, claritybot, Amazonbot Blocking No — crawling allowed
#
#                ..;coxkOOOOOOkxoc;'.
#             .:d0NWMMMMMMMMMMMMMMWN0xc'
#          .:kXMMMMMMMMMMMMMMMMMMMMMMMXl.
#        .c0WMMMMMMMMMMMMMMMMMMMMMMMXd'
#       ,OWMMMMMMMMMMMMMMMMMMMMMMMXo'       ..
#      cXMMMMMMXo::::::::::::::col.       .lKXl.
#     lNMMMMMMM0'                       .lKWMMNo
#    :XMMMMMMMM0'                     .l0WMMMMMNc
#   .OMMMMMMMMM0'     .ccccccc;.      ,KMMMMMMMMO.
#   :NMMMMMMMMM0'     oWMMMMMMWKc.     oWMMMMMMMN:
#   lWMMMMMMMMM0'     oWMMMMMMMMX:     ,KMMMMMMMMo
#   oMMMMMMMMMM0'     oWMMMMMMMMNc     ,KMMMMMMMMd
#   cNMMMMMMMMM0'     oWMMMMMMMNd.     lWMMMMMMMWl
#   '0MMMMMMMMWk.     ,oooooooc'      ,0MMMMMMMMK,
#    oWMMMMMMXo.                     ,0MMMMMMMMWo
#    .xWMMMXd'                     ,dXMMMMMMMMWk.
#     .xWNx'       .',''''''',,;coONMMMMMMMMMWk.
#      .:,       .l0WWWWWWWWWWWMMMMMMMMMMMMMNd.
#              .lKWMMMMMMMMMMMMMMMMMMMMMMMWk;
#            .lKWMMMMMMMMMMMMMMMMMMMMMMMNk;.
#            .ckXWMMMMMMMMMMMMMMMMMMWXkl'
#               .;ldO0XNWWWWWWNXKOxl;.
#                    ..'',,,,''..
#
#

# NOTE: Allow is a non-standard directive for robots.txt. It is allowed by Google bots. See https://developers.google.com/search/reference/robots_txt#allow

User-agent: *
# Crawl delay asks bots to wait this many seconds between requests. Ignored by google.
Crawl-delay: 5
Disallow: /admin/
Disallow: /newsletter/
Disallow: /healthcheck/
Disallow: /subpage/
Disallow: /ckeditor/
Disallow: /api/
Disallow: /static/images/
Disallow: /subscriber/
Disallow: /selfservice/
Disallow: /press-release/preview/
Disallow: /press-release/editor/

# no deep queries to search
Disallow: /search/*
Allow: /search/$

# don't index our dynamic images
Disallow: /user_media/
Disallow: /imgproxy/

# don't deep index topic pages
Disallow: /topic/?page=*

Allow: /sitemap.xml

#
# Rules for specific crawlers below. Note that these don't stack. If you create a specific user-agent rule
# you should copy the rules over from '*' above by hand.
#

# Allow Twitter to see all links
User-agent: Twitterbot
Crawl-delay: 5
Disallow:

# Allow Googlebot-News to see header images and favicons, BUT make it follow all the directives from our * group
# See below link for why we have to repeat these directives
# https://developers.google.com/search/reference/robots_txt#order-of-precedence-for-user-agents
User-agent: Googlebot-News
Disallow: /admin/
Disallow: /newsletter/
Disallow: /healthcheck/
Disallow: /subpage/
Disallow: /ckeditor/
Disallow: /api/
Disallow: /static/images/
Disallow: /subscriber/
Disallow: /selfservice/
Disallow: /press-release/preview/
Disallow: /press-release/editor/

# no deep queries to search
Disallow: /search/*
Allow: /search/$

Allow: /google_news_sitemap.xml
# Allow Google News to see header images and favicons
Allow: /user_media/
Allow: /imgproxy/
Allow: /static/images/favicons


# Googlebot-Image is now used for favicons. Allow it to see favicon-related files but nothing else
User-agent: Googlebot-Image
Disallow: /
Allow: /imgproxy/
Allow: /static/images/favicons
Allow: /favicon.ico
Allow: /white-favicon.ico
Allow: /apple-touch-icon.png
Allow: /favicon-32x32.png
Allow: /white-favicon-32x32.png
Allow: /favicon-16x16.png
Allow: /white-favicon-16x16.png
Allow: /site.webmanifest
Allow: /safari-pinned-tab.svg
Allow: /browserconfig.xml
Allow: /android-chrome-144x144.png
Allow: /mstile-150x150.png

# Don't let PetalBot crawl at all
User-agent: PetalBot
Disallow: /

# Block sentione.com
User-agent: sentibot
Disallow: /

# block seoclarity.net/bot.html
User-agent: claritybot
Disallow: /

# block omgili.com/crawler.html
User-Agent: omgilibot
Disallow: /
User-Agent: omgili
Disallow: /

# All Facebook crawler user-agent to see all
User-agent: facebookexternalhit/1.1
Disallow:

User-agent: AhrefsBot
# We want this bot to crawl way slower https://ahrefs.com/robot/
Crawl-Delay: 30

Disallow: /admin/
Disallow: /newsletter/
Disallow: /healthcheck/
Disallow: /subpage/
Disallow: /ckeditor/
Disallow: /api/
Disallow: /static/images/
Disallow: /subscriber/
Disallow: /selfservice/
Disallow: /press-release/preview/
Disallow: /press-release/editor/

# no deep queries to search
Disallow: /search/*
Allow: /search/$

# don't index our dynamic images
Disallow: /user_media/
Disallow: /imgproxy/

Disallow: /topic/
Disallow: /editors/

User-agent: Amazonbot
# Restrict what Amazonbot (Alexa) can see, and a
Crawl-Delay: 10

Disallow: /admin/
Disallow: /newsletter/
Disallow: /healthcheck/
Disallow: /subpage/
Disallow: /ckeditor/
Disallow: /api/
Disallow: /static/images/
Disallow: /subscriber/
Disallow: /selfservice/
Disallow: /press-release/preview/
Disallow: /press-release/editor/

# no deep queries to search
Disallow: /search/*
Allow: /search/$

# don't index our dynamic images
Disallow: /user_media/
Disallow: /imgproxy/

Disallow: /topic/
Disallow: /editors/
Disallow: /signup/*
Allow: /signup/$

User-agent: amazon-kendra # Amazon Kendra Web Crawler
Disallow: /

sitemap.xml 200 OK
Type Sitemap Index URLs 106 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.socialmediatoday.com/
200https://socialmediatoday.com/

HTTP → HTTPS

301http://socialmediatoday.com/ https://www.socialmediatoday.com/

Consistent

A
Domain Intelligence
socialmediatoday.com — via NameCheap, Inc., 20 years old
PASS
socialmediatoday.com — via NameCheap, Inc., 20 years old
Warning::
Domain expires in 77 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 8, 2026
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: NameCheap, Inc.
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.
Domain expiry

23 days

July 8, 2026

SSL certificate

31 days

Issued by Google Trust Services

Domain age

20 years

Registered July 8, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a06:98c1:3107::ac40:94bc

Registrar

NameCheap, Inc.

Unlocked 2 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 NameCheap, Inc.
Created July 8, 2006 (20 years ago)
Expires July 8, 2026 (2 months)
Last Updated June 8, 2025
Name Servers ivy.ns.cloudflare.com, sid.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2a06:98c1:3107::ac40:94bc
Data source: rdap (0.0s)

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

Connection waterfall

DNS Lookup 5 ms TCP Connect 1 ms TLS Handshake 10 ms Server Processing 20 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