Skip to content

Hostname

ellopos.net

Last fetched

ellopos.net resolves to 208.98.35.161, announced in 208.98.35.0/24 by SHARKTECH - Sharktech in US. ellopos.net 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 · ellopos.netRouting diversity1.5/10Peering density6.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/ellopos.net

Resolution chain

IPv6 resolution

No AAAA record for ellopos.net is recorded in WhisperGraph.

Attribution

sharktech

ORIGIN_AS

WHOIS identity

Registrar
iana:93
Registrant organisation
elloposnet
Contact emails
08b39c7ee1a7f467fbc132a088093a1d534c3f9f@whois.gkg.net, 116ea8db6ffb4a64cd7e3a412cacc57a70342947@whois.gkg.net, 7cf7dc0ec1f7965b36e85032353b0de238ceb1c5@whois.gkg.net, c1523522f0589e61029ebb77ece82fb25449cd0e@whois.gkg.net, dbf359796559ab28049651589e30fca2a5b160d2@whois.gkg.net, f2edf4203e92c1165cd8534c1fa25336e7c11499@whois.gkg.net, f77e97c2d1ce002fb378e33e00005e645bd8133a@whois.gkg.net

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

  • 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
  • ns1.site4now.net
  • ns2.site4now.net
  • ns3.site4now.net

MX records

  • igw13.site4now.net

SPF policy

  • a: ellopos.net
  • mx: ellopos.net
  • include: _spf.site4now.net

Threat-feed evidence

History

Related pages

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