Skip to content

Hostname

hideandsleep.com

Last fetched

hideandsleep.com resolves to 104.18.37.154, announced in 104.18.37.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. hideandsleep.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 · hideandsleep.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/hideandsleep.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:168
Registrant organisation
the travel chapter
Contact emails
vanillaholdings@gmail.com

Subdomains

Subdomain
e.hideandsleep.com
social.hideandsleep.com
www.hideandsleep.com

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • anuj.ns.cloudflare.com
  • desi.ns.cloudflare.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

  • mxa-00a4ed01.gslb.pphosted.com
  • mxb-00a4ed01.gslb.pphosted.com

SPF policy

  • mx: hideandsleep.com
  • include: spf.mandrillapp.com
  • include: spf.protection.outlook.com
  • include: spf.smtp2go.com
  • include: spf.exclaimer.net
  • ip: 146.177.3.123
  • ip: 162.13.251.248
  • ip: 162.13.251.254
  • ip: 162.13.54.24
  • ip: 213.152.51.49
  • ip: 37.188.109.182
  • ip: 69.20.41.227
  • ip: 8.31.233.118
  • ip: 8.31.233.120
  • ip: 8.31.233.121
  • ip: 8.31.233.22
  • ip: 80.229.255.98
  • ip: 81.136.153.118
  • ip: 81.138.71.89
  • ip: 92.207.168.98

Threat-feed evidence

History

Related pages

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