LOW: Spam URL Report



This report is the extraction of URLs and relays from Spam messages.

Sources and Extractions

We and several partners have Spam-pots (basic email addresses) in many places around the world. These accounts are not subscribed and most are not listed anywhere, so any email directed at them would be unrequested and can be considered Spam. We extract certain information from each of these messages, such as the last hop IP (which cannot be spoofed), the sending address (which can be anything and is frequently spoofed), any URLs, and the subject of the message.

We do not save the original messages, only the extractions, because due to the high quantity of messages and the amount of space they would take up, they do not have sufficient value.

False Positives

It is highly likely that non-malicious URLs end up on this report. In fact, we expect them regularly. The source of these URLs is still malicious, but many times Spam messages will include real or correct URLs to help hide the malicious ones that are also included in the messages. When users start looking at the different URLs included in a message, hiding one or two malicious ones amongst the real ones creates a greater environment of trust with the email recipient and will increase the odds of them clicking one of the malicious ones.

We do not filter out any URL we get for several reasons. Primarily, we do not really know which ones would be important for you to see and know about. We could filter out anything that is not specifically hostile, but it might be important for logging purposes. Or perhaps they are referencing your real login directions but redirecting the actual login somewhere else.

Areas of Concern

If the “src” IP is one of their systems, this means your email server was the one sending, routing, or forwarding the Spam messages. The URLs should be of interest even if they are not malicious; they might help guide you to the actual phishing target, or at least give you a heads up that the URL is being used in some sort of Spam/phishing attack. Extra traffic to those URLs might be indicative of some level of success, or testing.

Filename: spam_url


  • timestamp
    Timestamp of the message
  • url
    URL that was extracted from a Spam message
  • host
    Hostname of the URL location
  • ip
    IP of the URL
  • asn
    ASN where the IP resides
  • geo
    Country location of the IP
  • region
    Regional location of the IP
  • city
    City location of the IP
  • naics
    North American Industry Classification System Code
  • sector
    Sector of the IP
  • severity
    Severity level
  • port
  • tag
    Additional tag
  • source
    Source of information, if public
  • sender
    Sender email address if available
  • subject
    Subject of the Spam message
  • src_ip
    IP address of the Spam relay that delivered the message (last hop)
  • src_asn
    ASN of the relay IP
  • src_geo
    Country location of the Spam relay
  • src_region
    Regional location of the Spam relay
  • src_city
    City location of the Spam relay
  • src_naics
    North American Industry Classification System Code of relay
  • src_sector
    Sector of the spam relay (IP)


"2010-02-10 00:00:00",,node01.example.com,,64512,ZZ,Region,City,0,"Communications, Service Provider, and Hosting Service",low,443,,,,,,64512,ZZ,Region,City,0,
"2010-02-10 00:00:01",,node02.example.com,,64512,ZZ,Region,City,0,,low,443,,,,,,64512,ZZ,Region,City,0,
"2010-02-10 00:00:02",,node03.example.com,,64512,ZZ,Region,City,0,"Communications, Service Provider, and Hosting Service",low,443,,,,"[ Allenywander@outlook.com ]:  Automated Request [ 11/26/2023 11:39:16 a.m. ]",,64512,ZZ,Region,City,0,

Our 128 Report Types