Skip to content
https://middleeasteye.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 2 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
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
URL Variants
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.middleeasteye.net/
200https://middleeasteye.net/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://middleeasteye.net/ → https://middleeasteye.net/

Consistent

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

Certificate validity

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

Recommended actions

  • 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
4 A records, 38 ms lookup
PASS
4 A records, 38 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.2.191, 151.101.130.191, 151.101.66.191, 151.101.194.191
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2a04:4e42::703, 2a04:4e42:400::703, 2a04:4e42:600::703, 2a04:4e42:200::703
Info::
4 nameserver(s) configured
Got: ns-263.awsdns-32.com, ns-800.awsdns-36.net, ns-1667.awsdns-16.co.uk, ns-1159.awsdns-16.org
Info::
5 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: 38 ms
Got: 38 ms
A151.101.2.191, 151.101.130.191, 151.101.66.191, 151.101.194.191
AAAA2a04:4e42::703, 2a04:4e42:400::703, 2a04:4e42:600::703, 2a04:4e42:200::703
CNAME—
NSns-263.awsdns-32.com, ns-800.awsdns-36.net, ns-1667.awsdns-16.co.uk, ns-1159.awsdns-16.org
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
google-site-verification=38CoMj4V1Cx04EDapVEaSgBojYbb3QKuvGcGtnHAoR4
SPF v=spf1 include:_spf.google.com -all
google-site-verification=Lr8pruQpADJgaSF13uUaWrFKbhzxAMRmrMH0Y-ve53s
google-site-verification=QCF8ADD8HKbYPiKLj4VHjGZ18Dr9hJiy2qSCXJO_T3Q
google-site-verification=ElkQgR7wGhN6kIkPskg20yrGCNetApR5dv1N_KRTpZ4
facebook-domain-verification=vp54wf6hcd72hdggvxro3766ykxvrg
CAALookup not available with standard resolver
Resolved in 38 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), 75 ms total
PASS
1 redirect(s), 75 ms total
Info::
Single redirect
Got: https://middleeasteye.net → https://www.middleeasteye.net/ (301)
Info::
WWW normalization redirect

https://middleeasteye.net

7 ms · HTTP/1.1

301

https://www.middleeasteye.net/

68 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://middleeasteye.net3017 msHTTP/1.1
2https://www.middleeasteye.net/20068 msHTTP/1.1

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 2a04:4e42::703, 2a04:4e42:400::703, 2a04:4e42:600::703, 2a04:4e42:200::703
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a04:4e42::703, 2a04:4e42:400::703, 2a04:4e42:600::703, 2a04:4e42:200::703 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 36 URLs
PASS
robots.txt present, sitemap with 36 URLs
Info::
robots.txt is present
Got: 1799 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 36 entries
Info::
Sitemap index with 36 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 1799 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /client-access
Disallow: /client-reset
Disallow: /filter/tips
Disallow: /file/
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/file/
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed
sitemap.xml 200 OK
Type Sitemap Index URLs 36 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
middleeasteye.net — via GoDaddy.com, LLC, 12 years, 6 months old
PASS
middleeasteye.net — via GoDaddy.com, LLC, 12 years, 6 months old
Info::
Domain registered until Dec 3, 2033 (7 years, 8 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: GoDaddy.com, 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.
Domain expiry

2728 days

December 3, 2033

SSL certificate

65 days

Issued by Let's Encrypt

Domain age

12 years, 6 months

Registered December 3, 2013

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a04:4e42::703

Registrar

GoDaddy.com, LLC

Unlocked 4 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 GoDaddy.com, LLC
Created December 3, 2013 (12 years, 6 months ago)
Expires December 3, 2033 (7 years, 8 months)
Last Updated December 5, 2024
Name Servers ns-1159.awsdns-16.org, ns-1667.awsdns-16.co.uk, ns-263.awsdns-32.com, ns-800.awsdns-36.net
DNSSEC Not enabled
Hosting
IP Address 2a04:4e42::703
Data source: rdap (0.1s)

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 40 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
35 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.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
41 ms
Total Time Total request time from DNS lookup through full response.
41 ms

Connection waterfall

DNS Lookup 35 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 1 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