Skip to content

Hostname

notengo.com

Last fetched

notengo.com resolves to 44.227.65.245, announced in 44.224.0.0/11 by AMAZON-02 - Amazon.com, Inc. in US. notengo.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 · notengo.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/notengo.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1861
Registrant organisation
black bayou
Contact emails
notengo.com-registrant@fabulouswhoiscompliance.com, domains@black-bayou.com

Subdomains

Subdomain
miweb.notengo.com
not.notengo.com
notengo.notengo.com
ns1.notengo.com
ns2.notengo.com
sorry.notengo.com
ww.notengo.com
www.notengo.com
wwww.notengo.com

Showing 9 of 9 subdomains (9 per page).

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

  • curitiba.ns.porkbun.com
  • fortaleza.ns.porkbun.com
  • maceio.ns.porkbun.com
  • salvador.ns.porkbun.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

Threat-feed evidence

History

Related pages

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