Skip to content

Hostname

auth.pitea.xyz

Last fetched

auth.pitea.xyz resolves to 185.157.161.187, announced in 185.157.160.0/23 by OBEHOSTING - Obehosting AB in SE. auth.pitea.xyz 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 · auth.pitea.xyzRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.9/10canon.whisper.security/host/auth.pitea.xyz

Resolution chain

IPv6 resolution

No AAAA record for auth.pitea.xyz is recorded in WhisperGraph.

Attribution

obehosting

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for auth.pitea.xyz. 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.

Mail and authentication

Nameservers

  • ns.pite.biz
  • ns2.pite.biz
  • ns.helvetet.eu
  • ns2.helvetet.eu
  • 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
  • helvetet1.sytes.net
  • helvetet2.sytes.net
  • ns.pitea.xyz
  • ns2.pitea.xyz

MX records

  • mail.pitea.xyz

SPF policy

  • ip: 2001:470:deca::/48
  • include: _spf.google.com
  • include: spf.protection.outlook.com
  • include: _spf.online.superoffice.com
  • include: spf-b.telia.com
  • ip: 185.157.161.187

Threat-feed evidence

History

Related pages

Pivot from auth.pitea.xyz 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: "auth.pitea.xyz"})-[: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.