Skip to content

Hostname

adequatehosting.com

Last fetched

adequatehosting.com resolves to 15.204.55.124, announced in 15.204.0.0/17 by OVH - OVH SAS in US. adequatehosting.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 · adequatehosting.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/adequatehosting.com

Resolution chain

IPv6 resolution

No AAAA record for adequatehosting.com is recorded in WhisperGraph.

Attribution

ovh

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
master mail
Contact emails
adequatehosting@gmail.com, mastermailste2@gmail.com, 217c4e2638894ba8890ce0f0b9c6ec56.protect@withheldforprivacy.com, c4e6a4c69c884b9a8847753fb978da75.protect@withheldforprivacy.com

Subdomains

Mail and authentication

Nameservers

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • adequatehosting.com

SPF policy

  • ip: 15.204.34.36
  • ip: 188.165.140.197
  • ip: 188.165.140.208
  • ip: 205.185.123.59
  • ip: 209.141.43.58
  • ip: 209.141.45.144
  • ip: 209.141.53.78
  • ip: 209.141.59.217
  • ip: 213.255.226.105
  • ip: 213.255.226.106
  • ip: 213.255.226.107
  • ip: 216.75.63.134
  • ip: 51.158.21.240
  • ip: 65.255.34.3
  • ip: 65.255.34.4
  • ip: 65.255.34.6
  • ip: 98.142.108.66
  • ip: 98.142.108.67
  • ip: 98.142.108.68
  • ip: 98.142.108.69

Threat-feed evidence

History

Related pages

Pivot from adequatehosting.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: "adequatehosting.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.