Skip to content

Hostname

teenproblem.net

Last fetched

teenproblem.net resolves to 85.14.21.147, announced in 85.14.21.0/24 by EVOLINK-AS - Evolink EAD in BG. teenproblem.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 · teenproblem.netRouting diversity1.5/10Peering density8.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/teenproblem.net

Resolution chain

IPv6 resolution

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

Attribution

evolink ead

ORIGIN_AS

WHOIS identity

Registrar
iana:303
Registrant organisation
anton filipov
Contact emails
domains@investor.bg, vladi@investor.bg, gdpr-masking@gdpr-masked.com, contact@privacyprotect.org

Subdomains

Subdomain
admin.teenproblem.net
adminpanel.teenproblem.net
gw.teenproblem.net
m.teenproblem.net
mail.teenproblem.net
www.teenproblem.net

Showing 6 of 6 subdomains (6 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

  • redirns1.bgdns.net
  • redirns2.bgdns.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

MX records

  • m.ibg.bg

SPF policy

  • ip: 85.14.4.112/28
  • ip: 85.14.21.145/28
  • ip: 194.12.227.222/32
  • ip: 194.12.229.224/28
  • ip: 194.12.229.96/27
  • a: teenproblem.net
  • mx: teenproblem.net

Threat-feed evidence

History

Related pages

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