Skip to content

Hostname

servcity.org

Last fetched

servcity.org resolves to 163.5.76.34, announced in 163.5.76.0/24 by Blockchain-Creek - Blockchain Creek B.V. in NL. servcity.org 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 · servcity.orgRouting diversity1.5/10Peering density5.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/servcity.org

Resolution chain

IPv6 resolution

No AAAA record for servcity.org is recorded in WhisperGraph.

Attribution

blockchain creek

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
marek zarei
Contact emails
abuse@gohost.de

Subdomains

Subdomain
bus-nl-mep-512.servcity.org
clients.servcity.org
cryptopay1.servcity.org
cust.servcity.org
daserver1.servcity.org
dedi.servcity.org
email--ouptout-at-servcity-dot-org--.servcity.org
git.servcity.org
loadbalancer.servcity.org
mc-stats.servcity.org
ns-01.servcity.org
ns-02.servcity.org

Showing 12 of 76. View all subdomains →

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

  • ns1.ang1.de
  • ns3.ang1.de
  • ns-01.anschuetznet.de
  • ns-03.anschuetznet.de
  • 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

  • smtp-1.ang1.de

SPF policy

  • ip: 62.72.177.62

Threat-feed evidence

History

Related pages

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