On 2/1/2018 6:47 AM, Rich Shepard wrote:
>   A curios situation. The SQL Ledger fork, ledger123, died some time in the
[snip]
> 
>   'whois' shows:
> 
> Updated Date: 2018-01-22T01:04:39Z
> Creation Date: 2011-01-19T01:36:38Z
> Registry Expiry Date: 2019-01-19T01:36:38Z

There is absolutely zero correlation required between any of the
following:

1) whether or not a domain exists (as shown by whois)

2) whether it has a DNS entry

3) whether there is a web server running

4) whether there is a mailman server running

5) whether there is an SMTP server running to receive email

6) whether it is possible to send email that looks like it comes
   from that domain

For these six conditions:

1) The domain exists (is registered) and expires 2019-01-18

2) There is a DNS entry for domain, pointing to 209.99.64.25
   which resolves back to 209-99-64-25.fwd.datafoundry.com,
   which is owned by Confluence Networks

3) There appears to be a web server running, but it returns
   a blank page containing some Javascript that is supposed to
   load a "Domain Parked" notice but doesn't, at least on Firefox

4) Obviously, there is a mailman server still sending out the
   subscription notices. This is wholly independent of anything else,
   and it's probably running on the host that USED TO serve the website,
   or it could even be a completely different host somewhere else.

5) There is no MX entry in DNS for ledger123.org, so the fallback is
   to use the main address 209.99.64.25.  Attempting to telnet to
   port 25 at this IP address times out, so it appears there is no
   SMTP server available to receive email.  Sending email to
   <anything>@ledger123.org will sit in your outgoing queue until it
   times out, and then you'll receive a bounce.

6) Anybody can send email that LOOKS LIKE it came from ledger123.org


The crucial bit of information we don't have is in the headers of the
subscription emails you're receiving.  It would be the IP address of the
actual originating host.  Once you have that you could do a whois lookup
of the IP and figure out whom to contact about it.

_______________________________________________
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to