Skip to content

Hostname

freelancer.is

Last fetched

freelancer.is resolves to 100.49.167.133, announced in 100.48.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. freelancer.is 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 · freelancer.isRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/freelancer.is

Resolution chain

IPv6 resolution

IPv6 resolution is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

Attribution is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

WHOIS identity

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

Subdomains

Subdomains is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

Mail and authentication

Nameservers

  • ns-355.awsdns-44.com
  • ns-683.awsdns-21.net
  • ns-1144.awsdns-15.org
  • ns-1924.awsdns-48.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com

SPF policy

  • include: aspmx.googlemail.com
  • ip: 174.123.163.178
  • ip: 174.129.12.107
  • ip: 174.129.202.232
  • ip: 174.129.204.12
  • ip: 174.129.205.207
  • ip: 74.52.4.138

Threat-feed evidence

History

Related pages

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