Skip to content

Hostname

hotels.ng

Last fetched

hotels.ng resolves to 104.21.69.7, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. hotels.ng 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 · hotels.ngRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/hotels.ng

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
registrar:radix domains d/b/a radix.ng
Registrant organisation
mark essien
Contact emails
markessien@gmail.com

Subdomains

Subdomain
api.hotels.ng
assets.hotels.ng
autoconfig.hotels.ng
autodiscover.hotels.ng
blog.hotels.ng
booking.hotels.ng
bookly.hotels.ng
business.hotels.ng
cache.hotels.ng
crm.hotels.ng
image-redirect.hotels.ng
images.hotels.ng

Showing 12 of 40. 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

  • carter.ns.cloudflare.com
  • emily.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

  • work.timbu.cloud
  • mail.hotels.ng

SPF policy

  • include: work.timbu.cloud
  • include: amazonses.com
  • include: _spf.google.com
  • a: hotels.ng
  • mx: hotels.ng

Threat-feed evidence

History

Related pages

Pivot from hotels.ng 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: "hotels.ng"})-[: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.