Skip to content

Hostname

fiberdns.net

Last fetched

fiberdns.net resolves to 185.136.205.251, announced in 185.136.205.0/24 by FiberNET-Teknoloji-LTD - Mehmet Uzunca in TR. fiberdns.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 · fiberdns.netRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/fiberdns.net

Resolution chain

IPv6 resolution

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

Attribution

mehmet uzunca

ORIGIN_AS

WHOIS identity

Registrar
iana:1601
Registrant organisation
fiber server internet teknolojileri
Contact emails
mehmet_uzunca@hotmail.com, info@fiberserver.net.tr

Subdomains

Subdomain
c65583.fiberdns.net
c69972.fiberdns.net
cpanel.fiberdns.net
cpcalendars.fiberdns.net
cpcontacts.fiberdns.net
crm.fiberdns.net
fibercenter.fiberdns.net
fiberpanel.fiberdns.net
fr3.fiberdns.net
ftp.fiberdns.net
mail.fiberdns.net
ns1.fiberdns.net

Showing 12 of 51. View all subdomains →

Mail and authentication

Nameservers

  • tr21.fiberdns.net
  • tr22.fiberdns.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

  • mail.fiberdns.net

SPF policy

  • a: fiberdns.net
  • mx: fiberdns.net
  • ip: 178.32.6.204
  • ip: 179.61.128.156
  • ip: 179.61.128.185
  • ip: 179.61.130.155
  • ip: 179.61.130.188
  • ip: 185.136.205.117
  • ip: 185.136.205.118
  • ip: 185.136.205.251
  • ip: 191.96.191.192
  • ip: 45.80.172.250

Threat-feed evidence

History

Related pages

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