Skip to content
https://www.seogarden.net

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
8 PASS 8 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 152.53.127.135 does not match any cert SAN: web30.flamenetworks.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
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
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
1 A records, 69 ms lookup
PASS
1 A records, 69 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 152.53.127.135
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: seogarden.net
Info::
2 nameserver(s) configured
Got: heisenberg.flamedns.host, pinkman.flamedns.host
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 69 ms
Got: 69 ms
A152.53.127.135
AAAA—
CNAMEseogarden.net
NSheisenberg.flamedns.host, pinkman.flamedns.host
MX
1 SMTP.GOOGLE.COM
TXT
SPF v=spf1 +a +mx +a:web24.flamenetworks.com include:_spf.google.com -all
google-site-verification=ONw_ybQVxqjHri51JI6TsflVFvPUtQmOFhHSFEsg7pw
CAALookup not available with standard resolver
Resolved in 69 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

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A
Multi-Resolver DNS Speed
Mean 57ms across 3 resolvers (spread 77ms)
PASS
Mean 57ms across 3 resolvers (spread 77ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 54ms
Got: 54ms via 1.1.1.1:53
Info::
Quad9: 97ms
Got: 97ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.seogarden.net

https://www.seogarden.net

120 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.seogarden.net200120 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 4906 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 4906 B Sitemaps referenced 1 User-agents NetAnts, NICErsPRO, Stanford Comp Sci, suzuran, FreeFind, Jetbot, LexiBot, Teleport, TeleportPro, WWW-Collector-E, CheeseBot, CherryPickerElite, Ruby, FairAd Client, inoreader.com, MSIECrawler, Python-urllib, URL Control, PerMan, b2w, voilabot, WebSauger, Mail.RU_Bot, httplib, Openfind, Sogou, WebStripper, Foobot, MIIxpc, Updownerbot, Aqua_Products, Bullseye, calculon spider, Optimizer, sitebot, TheNomad, toCrawl, Wget, Xenu's, Flaming AttackBot, IDG, moget, sootle, VCI, Barkrowler, Gaisbot, larbin, LinkScan, Microsoft URL Control, PaperLiBot, SiteSnagger, coccoc, BLEXBot, Qwantify, hloader, Pu_iN Crawler, Bloglovin, ezooms, jikespider, NetMechanic, Alexibot, Bot, grub, OmniExplorer_Bot, Parser, sosospider, turingos, Mata Hari, Copernic, CopyRightCheck, exabot, Hatena Antenna, EroCrawler, grub-client, Pcore-HTTP, ProPowerBot, The Intraformant, Webster Pro, YandexMetrika, DotBot, humanlinks, Keyword Density, MegaIndex.ru, YaK, *, Baiduspider, BecomeBot, CherryPickerSE, spanner, URL_Spider_Pro, DittoSpyder, +https://www.megaindex.ru/, rogerbot, MJ12bot, Uptimebot, ExtractorPro, InfoNaviRobot, Openfind data gathere, proximic, SEOkicks, YisouSpider, EmailWolf, Nutch, Spinn3r, URLy Warning, Web Image Collector, Bookmark search tool, LinkWalker, Radiation Retriever, RepoMonkey, WebEnhancer, yodaobot, BackDoorBot, BlowFish, LinkextractorPro, Oracle Ultra Search, PHP, Trident, True_Robot, WebAuto, Daum, fatbot, GetRight, libWeb/clsHTTP, spbot, SeznamBot, Stanford, Szukacz, Crescent, Telesoft, WebBandit, WebCopier, WebVac, YandexTurbo, SEOkicks-Robot, BotALot, VCI WebViewer VCI WebViewer Win32, Website Quester, WordPress, CherryPicker, EmailCollector, Iron33, Mister PiX, pyton-requests, willybot, libwww-perl, ProWebWalker, RepoMonkey Bait & Tackle, asterias, BunnySlippers, SMTBot, SpankBot, Yandex, naver, searchpreview, cosmos, dumbot, Enterprise_Search, es, JennyBot, Kenjin Spider, lwp-trivial, WebZip, YandexBot, Linespider, AhrefsBot, Harvest, RMA, Offline Explorer, Openbot, psbot, QueryN Metasearch, Swiftbot, Zeus, python-requests, BuiltBotTough, EmailSiphon, LNSpiderguy Blocking No — crawling allowed
User-agent: *


Disallow: /author/

Disallow: /search/

Disallow: /plugins/

Disallow: /component/

Disallow: /item/

Disallow: /itemlist/

Disallow: */?fb_comment_id=

Disallow: */?type=

Disallow: */?tmpl=

Disallow: */?limitstart

Disallow: */?platform=

Disallow: */?wordfence_logHuman=

Disallow: */?utm_source=

Disallow: */?utm_content=



#SE

User-agent: Yandex

User-agent: YandexTurbo

User-agent: YandexBot

User-agent: Baiduspider


#User-agent: Slurp

# 202010

User-agent: Linespider

User-agent: Barkrowler

Disallow: /


#SEOTOOLS

User-agent: AhrefsBot

User-agent: BLEXBot

User-agent: DotBot

User-agent: MJ12bot

User-agent: proximic

User-agent: rogerbot

User-agent: YandexMetrika

#User-agent: Screaming Frog SEO Spider

User-agent: Xenu's

User-agent: SEOkicks

User-agent: SEOkicks-Robot

User-agent: YisouSpider

User-agent: Qwantify

User-agent: Uptimebot

Disallow: /


#SOCIAL

#User-agent: Twitterbot

#Disallow: /


#OTHER

User-agent: Ruby

User-agent: python-requests

User-agent: libwww-perl

User-agent: DotBot

User-agent: Mail.RU_Bot

User-agent: +https://www.megaindex.ru/

User-agent: Alexibot

User-agent: Aqua_Products

User-agent: asterias

User-agent: b2w

User-agent: BackDoorBot

User-agent: BecomeBot

User-agent: Bloglovin

User-agent: BlowFish

User-agent: Bookmark search tool

User-agent: Bot

User-agent: BotALot

User-agent: BuiltBotTough

User-agent: Bullseye

User-agent: BunnySlippers

User-agent: calculon spider

User-agent: CheeseBot

User-agent: CherryPicker

User-agent: CherryPickerElite

User-agent: CherryPickerSE

User-agent: coccoc

User-agent: Copernic

User-agent: CopyRightCheck

User-agent: cosmos

User-agent: Crescent

User-agent: Daum

User-agent: DittoSpyder

User-agent: dumbot

User-agent: EmailCollector

User-agent: EmailSiphon

User-agent: EmailWolf

User-agent: Enterprise_Search

User-agent: EroCrawler

User-agent: es

User-agent: exabot

User-agent: ExtractorPro

User-agent: ezooms

User-agent: FairAd Client

User-agent: fatbot

User-agent: Flaming AttackBot

User-agent: Foobot

User-agent: FreeFind

User-agent: Gaisbot

User-agent: GetRight

User-agent: grub

User-agent: grub-client

User-agent: Harvest

User-agent: Hatena Antenna

User-agent: hloader

User-agent: httplib

User-agent: humanlinks

User-agent: IDG

User-agent: InfoNaviRobot

User-agent: inoreader.com

User-agent: Iron33

User-agent: JennyBot

User-agent: Jetbot

User-agent: Jetbot

User-agent: jikespider

User-agent: Kenjin Spider

User-agent: Keyword Density

User-agent: larbin

User-agent: LexiBot

User-agent: libWeb/clsHTTP

User-agent: LinkextractorPro

User-agent: LinkScan

User-agent: LinkWalker

User-agent: LNSpiderguy

User-agent: lwp-trivial

User-agent: Mata Hari

User-agent: MegaIndex.ru

User-agent: Microsoft URL Control

User-agent: MIIxpc

User-agent: Mister PiX

User-agent: moget

User-agent: MegaIndex.ru

User-agent: spbot

User-agent: MSIECrawler

User-agent: naver

User-agent: NetAnts

User-agent: NetMechanic

User-agent: NICErsPRO

User-agent: Nutch

User-agent: Offline Explorer

User-agent: OmniExplorer_Bot

User-agent: Openbot

User-agent: Openfind 

User-agent: Openfind data gathere

User-agent: Optimizer

User-agent: Oracle Ultra Search

User-agent: Parser

User-agent: PaperLiBot

User-agent: Pcore-HTTP

User-agent: PerMan

User-agent: PHP

User-agent: ProPowerBot

User-agent: ProWebWalker

User-agent: psbot

User-agent: Pu_iN Crawler

User-agent: Python-urllib

User-agent: pyton-requests

User-agent: Qwantify

User-agent: QueryN Metasearch

User-agent: Radiation Retriever

User-agent: RepoMonkey

User-agent: RepoMonkey Bait & Tackle

User-agent: RMA

User-agent: searchpreview

User-agent: SeznamBot

User-agent: sitebot

User-agent: SiteSnagger

User-agent: SMTBot

User-agent: Sogou

User-agent: sootle

User-agent: sosospider

User-agent: SpankBot

User-agent: spanner

User-agent: Spinn3r

User-agent: Stanford

User-agent: Stanford Comp Sci

User-agent: suzuran

User-agent: Swiftbot

User-agent: Szukacz

User-agent: Teleport

User-agent: TeleportPro

User-agent: Telesoft

User-agent: The Intraformant

User-agent: TheNomad

User-agent: toCrawl

User-agent: Trident

User-agent: True_Robot

User-agent: turingos

User-agent: Updownerbot

User-agent: URL Control

User-agent: URL_Spider_Pro

User-agent: URLy Warning

User-agent: VCI

User-agent: VCI WebViewer VCI WebViewer Win32

User-agent: voilabot

User-agent: Web Image Collector

User-agent: WebAuto

User-agent: WebBandit

User-agent: WebCopier

User-agent: WebEnhancer

User-agent: WebSauger

User-agent: Website Quester

User-agent: Webster Pro

User-agent: WebStripper

User-agent: WebVac

User-agent: WebZip

User-agent: Wget

User-agent: willybot

User-agent: WordPress

User-agent: WWW-Collector-E

User-agent: yodaobot

User-agent: YaK

User-agent: Zeus

Disallow: /


Sitemap: https://www.seogarden.net/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 4 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::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.seogarden.net/
301https://seogarden.net/

Preferred variant: www

HTTP → HTTPS

301http://www.seogarden.net/ → https://www.seogarden.net/

Consistent

A+
Domain Intelligence
seogarden.net — via Internet Domain Service BS Corp, 15 years, 6 months old, hosted on netcup-AS - netcup GmbH, DE
PASS
seogarden.net — via Internet Domain Service BS Corp, 15 years, 6 months old, hosted on netcup-AS - netcup GmbH, DE
Info::
Domain registered until Jun 20, 2028 (1 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: Internet Domain Service BS Corp
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: netcup-AS - netcup GmbH, DE
Got: AS197540
Domain expiry

602 days

June 20, 2028

SSL certificate

170 days

Issued by SSL Corporation

Domain age

15 years, 6 months

Registered June 20, 2011

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

netcup-AS - netcup GmbH, DE

ASN AS197540

152.53.127.135

Registrar

Internet Domain Service BS Corp

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 Internet Domain Service BS Corp
Created June 20, 2011 (15 years, 6 months ago)
Expires June 20, 2028 (1 years, 8 months)
Last Updated September 29, 2026
Name Servers heisenberg.flamedns.host, pinkman.flamedns.host
DNSSEC Not enabled
Hosting
IP Address 152.53.127.135
ASN AS197540 (netcup-AS - netcup GmbH, DE)
Provider netcup-AS - netcup GmbH, DE
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 73 ms TCP Connect 30 ms TLS Handshake 33 ms Server Processing 31 ms Content Transfer 34 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback