Skip to content

Hostname

nelf.gov.ng

Last fetched

nelf.gov.ng resolves to 35.71.136.46, announced in 35.71.128.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. nelf.gov.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 · nelf.gov.ngRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/nelf.gov.ng

Resolution chain

IPv6 resolution

No AAAA record for nelf.gov.ng is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for nelf.gov.ng. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
devtest.nelf.gov.ng
edms.nelf.gov.ng
portal.nelf.gov.ng
slasapi.nelf.gov.ng
svs.nelf.gov.ng
verify.nelf.gov.ng
www.nelf.gov.ng

Showing 7 of 11. 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

  • ns1-02.azure-dns.com
  • ns4-02.azure-dns.info
  • ns2-02.azure-dns.net
  • 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
  • ns3-02.azure-dns.org

MX records

  • nelf-gov-ng.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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