Skip to content

Hostname

techjeny.org

Last fetched

techjeny.org resolves to 45.79.40.42, announced in 45.79.32.0/19 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. techjeny.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 · techjeny.orgRouting diversity1.5/10Peering density6.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/techjeny.org

Resolution chain

IPv6 resolution

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

Attribution

akamai

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
domains by proxy,
Contact emails
techjeny.org@domainsbyproxy.com

Subdomains

Subdomain
autoconfig.techjeny.org
autodiscover.techjeny.org
cpanel.techjeny.org
cpcalendars.techjeny.org
cpcontacts.techjeny.org
mail.techjeny.org
webdisk.techjeny.org
webmail.techjeny.org
www.techjeny.org

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

  • ns1.natxult1.armadaservers.com
  • ns2.natxult1.armadaservers.com
  • 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

  • techjeny.org

SPF policy

  • include: spf.antispamcloud.com
  • a: techjeny.org
  • mx: techjeny.org
  • ip: 45.79.40.42

Threat-feed evidence

History

Related pages

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