Skip to content

Hostname

informationng.com

Last fetched

informationng.com resolves to 104.21.63.62, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. informationng.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 · informationng.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/informationng.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1910
Registrant organisation
kingsley ezeani
Contact emails
kingz4kingus@yahoo.com, 0c87f618b2d14a3c8c31a415b9c84601.protect@whoisguard.com, 13c2264fcf404a76b015b40fa84e4a0d.protect@whoisguard.com, 3a216010e6a84e16b0157414aea1c634.protect@whoisguard.com, 61a085bf5e4d4406a7373728c03c0edb.protect@whoisguard.com, 62c94a00576c4831a8078239e60b9e9e.protect@whoisguard.com, 77800f6d67154256b0d342f19740d93d.protect@whoisguard.com, 79a7575a733a450cb8da22e607a1df2d.protect@whoisguard.com, 9adfc75ada754423872e4e0e432e4b66.protect@whoisguard.com, 9bc71585c4a548db947d42533ee943b5.protect@whoisguard.com, ca4fce17ab1140cdbad7d883f7e1d983.protect@whoisguard.com, d9dbce56af0b4e77a50a15135db332dd.protect@withheldforprivacy.com

Subdomains

Web-graph footprint

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

Mail and authentication

Nameservers

  • jay.ns.cloudflare.com
  • vera.ns.cloudflare.com

MX records

  • _dc-mx.ca45e0519b77.informationng.com

SPF policy

  • include: _spf.elasticemail.com
  • a: informationng.com
  • mx: informationng.com
  • include: spf.mailjet.com
  • include: spf.mandrillapp.com
  • ip: 162.255.160.168

Threat-feed evidence

History

Related pages

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