Skip to content
Install MCP

Hostname

turbo-web.com

Last fetched

turbo-web.com resolves to 13.226.244.124, announced in 13.226.244.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. turbo-web.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · turbo-web.comRouting diversity1.5/10Peering density9.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/turbo-web.com

Resolution chain

IPv6 resolution

No AAAA record for turbo-web.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:49
Registrant organisation
p.d.f.
Contact emails
turbo-web.com@whoisprotectservice.com, endo-pdf@bc4.so-net.ne.jp

Subdomains

Subdomain
admin.turbo-web.com
contact.turbo-web.com
j.turbo-web.com
m.turbo-web.com
mail.turbo-web.com
mail01.turbo-web.com
mail02.turbo-web.com
photobook.turbo-web.com
sp.turbo-web.com
taboland.turbo-web.com
www.turbo-web.com

Showing 11 of 13. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-344.awsdns-43.com
  • ns-971.awsdns-57.net
  • ns-1460.awsdns-54.org
  • ns-1712.awsdns-22.co.uk

MX records

  • mail01.turbo-web.com
  • mail02.turbo-web.com

SPF policy

  • ip: 202.32.140.0/25
  • ip: 52.199.245.138/32
  • ip: 52.198.46.58/32
  • include: spf.sme.co.jp
  • include: spf.tapirs.co.jp
  • include: fc0419.cuenote.jp
  • ip: 52.69.177.193
  • ip: 52.69.62.171

Threat-feed evidence

History

Related pages

Pivot from turbo-web.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "turbo-web.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.