Skip to content

Hostname

clearverify.com.ng

Last fetched

clearverify.com.ng resolves to 85.25.46.130, announced in 85.25.46.0/24 by VELIANET-AS - velia.net Internetdienste GmbH in FR. clearverify.com.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 · clearverify.com.ngRouting diversity1.5/10Peering density4.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/clearverify.com.ng

Resolution chain

IPv6 resolution

No AAAA record for clearverify.com.ng is recorded in WhisperGraph.

Attribution

velia net internetdienste

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
registrar:truehost cloud
Registrant organisation
aliyu idris
Contact emails
abbasidris2018@gmail.com, yamalacrc@gmail.com

Subdomains

Subdomain
admin.clearverify.com.ng
cpanel.clearverify.com.ng
cpcalendars.clearverify.com.ng
cpcontacts.clearverify.com.ng
mail.clearverify.com.ng
webdisk.clearverify.com.ng
webmail.clearverify.com.ng
www.clearverify.com.ng

Showing 8 of 9. View all subdomains →

Mail and authentication

Nameservers

  • dns3.afeeshost.com
  • ns3.afeeshost.com
  • ns4.afeeshost.com
  • dns1.afeeshost.ltd
  • dns2.afeeshost.ltd
  • 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

  • clearverify.com.ng

SPF policy

  • include: mailbaby.net
  • include: relay.mailbaby.net
  • include: spf-c.mailbaby.net
  • include: mailchannels.net
  • a: clearverify.com.ng
  • mx: clearverify.com.ng
  • ip: 85.25.46.130

Threat-feed evidence

History

Related pages

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